[MGNLDATA-261] Migration diffs when migrating from 4.5 to 5.2.x Created: 04/Aug/14  Updated: 29/Oct/15  Resolved: 07/Aug/14

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 2.2, 2.3
Fix Version/s: 2.2.4, 2.3.2

Type: Bug Priority: Major
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: migration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLDATA-257 Cannot start companyApp after update ... Closed
dependency
depends upon MGNLUI-3085 ContentAppMigrationTask uses QueryTas... Closed
depends upon MAGNOLIA-5857 Provide a NodeVisitorTask and emphasi... Closed
supersession
is superseded by MGNLDATA-262 Remaining activate/deactive commands ... Closed
Template:
Acceptance criteria:
Empty
Epic Link: Migration (4.5 to 5.2.x)

 Description   

As mentioned in cloned ticket comments:

It appeared QueryTasks are rather unsafe to use in deltas, there we cannot guarantee unsaved changes in current session will be processed.

Concretely, in case of migration from 4.5 to 5.2.x, data apps created by the DataTypesToContentAppsTask are not yet persisted in the workspace and may NOT be accounted for by the query.

There is at least one query-based task in data module itself as well: MigrateEditDataActionSubAppMappingConfiguration, which does correspond to the following diff output: http://jenkins.magnolia-cms.com/job/int_migration-tests_4.5-to-5.2.x-branch/Diff_Reports/config.modules.data.html

Side note, NodeVisitorTask needs to be backported to 5.2.x beforehand.



 Comments   
Comment by Mikaël Geljić [ 07/Aug/14 ]

Fixes made against 2.3.
Backport to 2.2 will be more simple: only adjusting MigrateEditDataActionSubAppMappingConfiguration as NodeVisitorTask and reapplying it in 2.2.4 delta.

Generated at Mon Feb 12 05:12:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.