[
https://issues.apache.org/jira/browse/UNOMI-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Griffon updated UNOMI-593:
--------------------------------
Description:
After a migration {{conditionTypes}} and {{actionTypes}} are not migrated
properly.
This happens because the file name of the mapping from
{{src/main/resources/META-INF/cxs/mappings}} is use to get the type of object
to migrate.
Here the inconsistencies:
|*Mapping (1.5.7)*|*Type (1.4.4)*|*Potential issue*|
|actiontype.json|actionType|*{color:#ff0000}YES{color}*|
|campaign.json|campaign| |
|campaignevent.json|campaignevent| |
|conditiontype.json|conditionType|{color:#ff0000}*YES*{color}|
|event.json|event| |
|exportconfig.json|exportConfig|*{color:#ff0000}YES{color}*|
|geonameEntry.json|geonameEntry| |
|goal.json|goal| |
|importconfig.json|importConfig|*{color:#ff0000}YES{color}*|
|patch.json|patch| |
|persona.json|persona| |
|personaSession.json|personaSession| |
|profile.json|profile| |
|propertyType.json|propertyType| |
|rule.json|rule| |
|rulestats.json|rulestats| |
|scoring.json|scoring| |
|segment.json|segment| |
|session.json|session| |
|userList.json|userList| |
h2. Potential issues
If one provides its own conditionType or actionTypes, or if one applied patch
on one of those objects, the migration will miss some data.
h2. Fix on migrated environment
Redeploy conditionTypes and actionTypes to recreate the objects.
For applied patch, remove the patch index, then reapply patch.
h2. Fix for next migration
Rename files to match object types
actiontype.json => actionType.json
conditiontype.json => conditionType.json
exportconfig.json => exportConfig.json
importconfig.json => importConfig.json
was:
After a migration {{conditionTypes}} and {{actionTypes}} are not migrated
properly.
This happens because the file name of the mapping from
{{src/main/resources/META-INF/cxs/mappings}} is use to get the type of object
to migrate.
Here the inconsistencies:
|*Mapping (1.5.7)*|*Type (1.4.4)*|*Potential issue*|
|actiontype.json|actionType|*{color:#FF0000}YES{color}*|
|campaign.json|campaign| |
|campaignevent.json|campaignevent| |
|conditiontype.json|conditionType|{color:#FF0000}*YES*{color}|
|event.json|event| |
|exportconfig.json| | |
|geonameEntry.json|geonameEntry| |
|goal.json|goal| |
|importconfig.json| | |
|patch.json|patch| |
|persona.json|persona| |
|personaSession.json|personaSession| |
|profile.json|profile| |
|propertyType.json|propertyType| |
|rule.json|rule| |
|rulestats.json|rulestats| |
|scoring.json|scoring| |
|segment.json|segment| |
|session.json|session| |
|userList.json|userList| |
h2. Potential issues
If one provides its own conditionType or actionTypes, or if one applied patch
on one of those objects, the migration will miss some data.
h2. Fix on migrated environment
Redeploy conditionTypes and actionTypes to recreate the objects.
For applied patch, remove the patch index, then reapply patch.
h2. Fix for next migration
Rename files to match object types
actiontype.json => actionType.json
conditiontype.json => conditionType.json
> Missing indices migration from 1.4.x to 1.5.x
> ----------------------------------------------
>
> Key: UNOMI-593
> URL: https://issues.apache.org/jira/browse/UNOMI-593
> Project: Apache Unomi
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: David Griffon
> Assignee: David Griffon
> Priority: Major
>
> After a migration {{conditionTypes}} and {{actionTypes}} are not migrated
> properly.
> This happens because the file name of the mapping from
> {{src/main/resources/META-INF/cxs/mappings}} is use to get the type of object
> to migrate.
> Here the inconsistencies:
> |*Mapping (1.5.7)*|*Type (1.4.4)*|*Potential issue*|
> |actiontype.json|actionType|*{color:#ff0000}YES{color}*|
> |campaign.json|campaign| |
> |campaignevent.json|campaignevent| |
> |conditiontype.json|conditionType|{color:#ff0000}*YES*{color}|
> |event.json|event| |
> |exportconfig.json|exportConfig|*{color:#ff0000}YES{color}*|
> |geonameEntry.json|geonameEntry| |
> |goal.json|goal| |
> |importconfig.json|importConfig|*{color:#ff0000}YES{color}*|
> |patch.json|patch| |
> |persona.json|persona| |
> |personaSession.json|personaSession| |
> |profile.json|profile| |
> |propertyType.json|propertyType| |
> |rule.json|rule| |
> |rulestats.json|rulestats| |
> |scoring.json|scoring| |
> |segment.json|segment| |
> |session.json|session| |
> |userList.json|userList| |
> h2. Potential issues
> If one provides its own conditionType or actionTypes, or if one applied patch
> on one of those objects, the migration will miss some data.
> h2. Fix on migrated environment
> Redeploy conditionTypes and actionTypes to recreate the objects.
> For applied patch, remove the patch index, then reapply patch.
> h2. Fix for next migration
> Rename files to match object types
> actiontype.json => actionType.json
> conditiontype.json => conditionType.json
> exportconfig.json => exportConfig.json
> importconfig.json => importConfig.json
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
