[MGNLUI-3085] ContentAppMigrationTask uses QueryTasks and results in incomplete updates when updating straight from 4.5 to 5.3 Created: 30/Jul/14  Updated: 29/Oct/15  Resolved: 06/Aug/14

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: 5.3
Fix Version/s: 5.3.2

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

Issue Links:
dependency
is depended upon by MGNLDATA-257 Cannot start companyApp after update ... Closed
is depended upon by MGNLDATA-261 Migration diffs when migrating from 4... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Migration (4.5 to 5.3.x)

 Description   

The ContentAppMigrationTask between 5.2.x and 5.3 uses a bunch of QueryTasks as subtasks. Because JCR queries may NOT account for unsaved changes in current session (see MAGNOLIA-5857), this results in incomplete updates for some modules, when updating straight from 4.5 to 5.3.

We should replace these QueryTasks with newly-introduced NodeVisitorTask.


Generated at Mon Feb 12 09:03:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.