[MGNLPCK-32] Overriding of updated nodes leads to loss of children Created: 01/Dec/09  Updated: 15/Sep/15  Resolved: 01/Dec/09

Status: Closed
Project: Packager (closed)
Component/s: None
Affects Version/s: 4.0
Fix Version/s: 4.0.1

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently when packager updates the nodes, if such nodes have matching UUIDs it will completely replace the node using session import and IMPORT_UUID_COLLISION_REPLACE_EXISTING import behavior. This leads to the loss of the existing children as the imported node doesn't have any (Packager would import child nodes separately). This import however happens only after the nodes have been already evaluated, which results in loss of child node in case this was earlier evaluated as unchanged, while it's parent was evaluated as changed.
The solution to the issue for now is to treat the nodes with matching UUIDs same way as those without matching UUIDs - just update all properties as appropriate, but do not replace whole node.



 Comments   
Comment by Jan Haderka [ 01/Dec/09 ]

Done as of r30045.

Comment by Michael Mühlebach [ 15/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

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