[MAGNOLIA-6933] MigrateVersionWorkspacesToNewStructureTask fails in case where moved node has same name as the new generated parent Created: 25/Jan/17  Updated: 16/May/17  Resolved: 13/Feb/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5, 5.5.1
Fix Version/s: 5.5.2

Type: Bug Priority: Blocker
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-7006 same name siblings issue in MigrateVe... Closed
causality
caused by MAGNOLIA-6774 Same uuids in multiple workspaces lea... Closed
dependency
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
Date of First Response:
Sprint: Kromeriz 83
Story Points: 5

 Description   

The versioned nodes are being moved to another location and the path of the current versioned node is /19, while the new path, being calculated from this versioned node uuid, is /19/33/44 (current uuid is like 19xxxx-33xxxx-44xxx-etc). While moving the former under the later we've met JCR consistency restriction, that the source path is an ancestor of destination path.
And also set debug level for the warn messages to prevent flooding the log.


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