[TINKERPOP-326] Traversal.reverse()

• Type: Bug
• Status: Closed
• Resolution: Done
• Fix Version/s: 3.0.0-incubating
• Component/s: process
• Assignee: Marko A. Rodriguez
• Reporter: Matthias Broecheler
• Created: 05/Nov/14 21:07
• Updated: 24/Mar/15 19:00
• Resolved: 24/Mar/15 19:00

Description

currently calls reverse() on each step. While that has the right semantics in some cases, i.e.

v.outE('knows').has('weight',5).inV

gets reversed to:

v.inE('knows').has('weight',5).outV

More complex traversals don't get reversed correctly:

v.outE('knows').has('weight',5).inV.outE('married').interval('since',0,10).inV

becomes

v.inE('knows').has('weight',5).outV.inE('married').interval('since',0,10).outV

whereas the "married" and "knows" should be flipped. Hence, more thought needs to be given to traversal reversal in the general case.