You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2022/07/19 15:58:00 UTC

[jira] [Created] (UNOMI-629) Cleanup old mergedWith code and do better migration for profile aliases

Kevan Jahanshahi created UNOMI-629:
--------------------------------------

             Summary: Cleanup old mergedWith code and do better migration for profile aliases
                 Key: UNOMI-629
                 URL: https://issues.apache.org/jira/browse/UNOMI-629
             Project: Apache Unomi
          Issue Type: Bug
    Affects Versions: 2.0.0
            Reporter: Kevan Jahanshahi
             Fix For: 2.0.0


The alias system on profile is new in Unomi 2.0.0 and the migration code seem's not correct or incomplete:

The migration to Aliases should do the following:
 * For each profiles that contains a *mergedWith* property we should retrieve the new master profile. Then we should create an Alias:

{  "_source": {    "itemId": "OLD_PROFILE_ID",    "itemType": "profileAlias",    "profileID": "MASTER_PROFILE_ID",    "clientID": "defaultClientId"  }
} * Also the profiles with mergedWith property can be removed by the migration (after that the alias for them have been created)
 * No alias should be created if profile have not been merged !
 * Also there is dead code in the ContextEndPoint related to mergedWith, this code should be cleaned and removed as this property no longer exists, and is no longer used by merge mechanisms.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)