[
https://issues.apache.org/jira/browse/UNOMI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Gerthoffert 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 during migration, rename one of the two with _NUMBER
on the fly, and log the change as a WARNING.
Make sure to handle objects that were created programmatically
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 during migration, rename one of the two with _NUMBER
on the fly, and log the change as a WARNING.
> 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
>
> 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 during migration, rename one of the two with
> _NUMBER on the fly, and log the change as a WARNING.
> Make sure to handle objects that were created programmatically
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
