[
https://issues.apache.org/jira/browse/TINKERPOP-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentyn Kahamlyk reopened TINKERPOP-2964:
------------------------------------------
> Many TraversalParent's steps have a replaceLocalChild logic that can result
> in a new ChildTraversal having an ID that already exists.
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TINKERPOP-2964
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2964
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.6.0
> Reporter: Jianzhong Liu
> Assignee: Valentyn Kahamlyk
> Priority: Critical
> Fix For: 3.7.1
>
>
> 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.]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
