[TINKERPOP-2964] Many TraversalParent's steps have a replaceLocalChild logic that can result in a new ChildTraversal having an ID that already exists.

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.6.0
• Fix Version/s: 3.6.6, 3.7.1
• Component/s: process
• Assignee: Valentyn Kahamlyk
• Reporter: Jianzhong Liu
• Created: 05/Jul/23 19:19
• Updated: 26/Oct/23 20:45
• Resolved: 26/Oct/23 20:45

Description

Following the invocation of replaceLocalChild, the new childTraversal within many steps can have an ID that already exists. For instance, in the TreeStep traversal ring replace logic, the 'integrateChild' function should be called prior to assigning it the new traversal. More details can be found in the Apache TinkerPop code at this link: https://github.com/apache/tinkerpop/blob/master/gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/step/map/TreeStep.java#L68-L72.