Details
-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Description
AT:
- To prevent redindexing the same index several times, we should use an ingest pipeline per release
- each migration task will be implemented as an processor
As a rough guideline the upgrade might be performed like this with piplines in place per type:
// #1 create target index with new mappings per type
// #2 create ingest pipeline for the migration fromVerion->toVersion with potential document modification processors per type
// #3 execute reindex per type using pipeline
// #4 delete ingest pipeline
// #5 update the alias to point to target index and remove alias from old index
// #5 delete old index
Note:
we could also postpone the alias switch and the delete of the old index to the very end of the upgrade, after all types have been migrated and only then update the alias + update the version in metadata + delete old indexes. This will ensure the upgrade is failsafe and we never end up with an inconsistent state of some indexes migrated and other not.
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- depends on
-
-
- Done
-