[MGNLMIGRATION-219] PostMigration task can return an already exist item exception Created: 30/Jan/13  Updated: 07/Feb/13  Resolved: 01/Feb/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: Samuel Schmitt Assignee: Samuel Schmitt
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

bootstrap under the migration folder should not throw a "already exist" exception.



 Comments   
Comment by Jan Haderka [ 31/Jan/13 ]

It should not assign new UUIDs automatically either. Either you are re-bootstrapping existing nodes in this task in which case it should remove existing or those are new nodes where you should not have problem in the first place.
With your change task would break any and all content that depends on UUID link and you would not even notice that.

Generated at Mon Feb 12 10:18:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.