[
https://issues.apache.org/jira/browse/UNOMI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Jahanshahi updated UNOMI-737:
-----------------------------------
Description:
Provide migration scripts to reindex previously existing unomi items in the new
single index.
*The migration could also check that all IDs of all items that will be moved to
the single-index are uniques, to avoid conflicts and overriding things without
being notified.*
If there is an ID conflict, rename one of the two with _NUMBER on the fly, and
log the change as a WARNING.
Check IDs before starting the re-index, to rename the ID before triggering the
re-index, to avoid conflicts during reindex.
Make sure to handle objects that were created programmatically
h1. IMPORTANT TO READ special handling for some items:
* groovy action itemID was overlapping the actionType itemID, so existing
groovyAction itemID should be updated during the migration by adding the
suffix: *-groovySourceCode*
* rulestat and rule have the same overlapping, so every rulestat itemID should
be updated by adding the suffix: *-stat*
** _Other option: do not migrate the rulestats, just delete the index, they
will be recreated. (not sure if anybody is using those statistics.)_
was:
Provide migration scripts to reindex previously existing unomi items in the new
single index.
*The migration could also check that all IDs of all items that will be moved to
the single-index are uniques, to avoid conflicts and overriding things without
being notified.*
If there is an ID conflict, rename one of the two with _NUMBER on the fly, and
log the change as a WARNING.
Check IDs before starting the re-index, to rename the ID before triggering the
re-index, to avoid conflicts during reindex.
Make sure to handle objects that were created programmatically
> Metadata Items: indices reduction migration
> -------------------------------------------
>
> Key: UNOMI-737
> URL: https://issues.apache.org/jira/browse/UNOMI-737
> Project: Apache Unomi
> Issue Type: Task
> Reporter: Kevan Jahanshahi
> Priority: Major
> Fix For: unomi-2.2.0
>
>
> Provide migration scripts to reindex previously existing unomi items in the
> new single index.
> *The migration could also check that all IDs of all items that will be moved
> to the single-index are uniques, to avoid conflicts and overriding things
> without being notified.*
> If there is an ID conflict, rename one of the two with _NUMBER on the fly,
> and log the change as a WARNING.
> Check IDs before starting the re-index, to rename the ID before triggering
> the re-index, to avoid conflicts during reindex.
> Make sure to handle objects that were created programmatically
> h1. IMPORTANT TO READ special handling for some items:
> * groovy action itemID was overlapping the actionType itemID, so existing
> groovyAction itemID should be updated during the migration by adding the
> suffix: *-groovySourceCode*
> * rulestat and rule have the same overlapping, so every rulestat itemID
> should be updated by adding the suffix: *-stat*
> ** _Other option: do not migrate the rulestats, just delete the index, they
> will be recreated. (not sure if anybody is using those statistics.)_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
