[
https://issues.apache.org/jira/browse/UNOMI-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699096#comment-17699096
]
Kevan Jahanshahi commented on UNOMI-727:
----------------------------------------
So here is a status of Unomi merge improvements:
* PR is available for review: [https://github.com/apache/unomi/pull/588]
** Merge action refactored and cleaned
** A lot more integrations tests
* 2 Unomi tickets created:
** https://issues.apache.org/jira/browse/UNOMI-748 : related to
update/OOM/bulkProcessor discussion
** https://issues.apache.org/jira/browse/UNOMI-749 : a new one ! discovered
by my new tests (past sessions rewrite after merge is producing inconsistent
profileId/profile for those past sessions)
2 tickets are not related to the PR, actually those issues was existing already
before, merge system should work exactly like before.
> Session/Event index rollover: fix merge system
> ----------------------------------------------
>
> Key: UNOMI-727
> URL: https://issues.apache.org/jira/browse/UNOMI-727
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: Kevan Jahanshahi
> Priority: Major
> Fix For: unomi-2.2.0
>
>
> The merge system is rewriting all existing events/sessions with the new
> profile ID.
> But due to session and event index rollover implem the merge could be broken
> on that part.
> ToDo in current ticket:
> * review existing tests and add new tests if necessary
> * fix merge if necessary by doing update by query on events/sessions indices
> * fix itests or add new itests if they are missing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
