[MAGNOLIA-7006] same name siblings issue in MigrateVersionWorkspacesToNewStructureTask and in CopyUtil Created: 12/Apr/17  Updated: 02/Jan/18  Resolved: 10/May/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5.2, 5.5.3
Fix Version/s: 5.5.4

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

Issue Links:
Relates
relates to MAGNOLIA-6933 MigrateVersionWorkspacesToNewStructur... Closed
relates to MAGNOLIA-7230 Incorrect task order of MigrateVersio... Open
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 95
Story Points: 5

 Description   

As we got move node error due to 'an item with the same name already present' here:

Caused by: javax.jcr.ItemExistsException: The move operation was not completed due to an item with the same name already present.
	at info.magnolia.jcr.wrapper.MagnoliaSessionWrapper.move(MagnoliaSessionWrapper.java:63)
	at info.magnolia.jcr.util.NodeUtil.moveNode(NodeUtil.java:523)
	at info.magnolia.setup.MigrateVersionWorkspacesToNewStructureTask.doExecute(MigrateVersionWorkspacesToNewStructureTask.java:154)
	at info.magnolia.module.delta.AbstractRepositoryTask.execute(AbstractRepositoryTask.java:57)

Probably MigrateVersionWorkspacesToNewStructureTask.getSavePath(Node) algorithm is not a complete solution to customers who have a large amount of data to migrate.

Same can happen in CopyUtil

javax.jcr.ItemExistsException: The move operation was not completed due to an item with the same name already present.
        at info.magnolia.jcr.wrapper.MagnoliaSessionWrapper.move(MagnoliaSessionWrapper.java:63)
        at info.magnolia.jcr.util.NodeUtil.moveNode(NodeUtil.java:523)
        at info.magnolia.cms.core.version.CopyUtil.moveChildren(CopyUtil.java:391)
        at info.magnolia.cms.core.version.CopyUtil.moveChildren(CopyUtil.java:389)
        at info.magnolia.cms.core.version.CopyUtil.importNode(CopyUtil.java:378)
        at info.magnolia.cms.core.version.CopyUtil.doImport(CopyUtil.java:149)


 Comments   
Comment by Julian Nodarse [ 21/Apr/17 ]

We have another report of a similar issue found here: SUPPORT-7489 .

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