[TINKERPOP-1727] Bytecode object shallow copied when traversals are cloned

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0, 3.2.5
• Fix Version/s: 3.3.0, 3.2.6
• Component/s: process
• Assignee: Ted Wilmes
• Reporter: Ted Wilmes
• Created: 13/Jul/17 16:39
• Updated: 19/Jul/17 12:43
• Resolved: 19/Jul/17 12:43

Description

The bytecode member of traversal objects are only shallow copied when a traversal is cloned. This causes issues because any updates to the clone will be propagated to cloned traversal.

gremlin> g = TinkerGraph.open().traversal()
==>graphtraversalsource[tinkergraph[vertices:0 edges:0], standard]
gremlin> traversal = g.V().out();null
==>null
gremlin> clonedTraversal = traversal.asAdmin().clone();null
==>null
gremlin> clonedTraversal.out().out();null
==>null
gremlin> traversal.getBytecode()
==>[[], [V(), out(), out(), out()]]
gremlin> clonedTraversal.getBytecode()
==>[[], [V(), out(), out(), out()]]

Issue Links

• links to: GitHub Pull Request #676