[
https://issues.apache.org/jira/browse/TINKERPOP-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP-1186.
-----------------------------------------
Resolution: Won't Fix
Assignee: Marko A. Rodriguez
Doing a bidirectional cloning is too expensive. A "complete clone" must happen
at the root traversal. For {{XXXVertexProgram}}, {{PureTraversal}} is used to
manage psuedo-clones.
> Solve the child traversal clone problem.
> ----------------------------------------
>
> Key: TINKERPOP-1186
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1186
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.1.1-incubating
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
>
> Assume the following traversals.
> {code}
> root = [RepeatStep([VertexStep,PropertiesStep])]
> child = [VertexStep,PropertiesStep]
> {code}
> where child is inside of root.
> Right now if you {{child.clone()}}, root is not cloned and thus, if you have
> multiple clone'd children, they all share the same root.
> This is bad as this is not a legitimate clone. We have never run into any
> bugs around this because all our code clones root traversals. However, when
> we introduced {{XXXVertexProgramStep}}, where children are cloned to the
> respective {{XXXVertexProgram}}, the problem emerged. We have a some
> workarounds currently, but we should really solve the general problem of
> ensuring the you get both an "up and down"-cascading clone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
