[TINKERPOP-736] Automatic Traversal rewriting

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Do
• Affects Version/s: 3.0.2-incubating
• Component/s: process
• Assignee: Unassigned
• Reporter: Matthias Broecheler
• Created: 18/Jun/15 04:13
• Updated: 25/Sep/24 18:13
• Resolved: 25/Sep/24 18:13

Description

Currently, Matchstep expects the pattern to be defined in terms of normalized traversals, that is, only the start and end of the traversal can be variables.
In order to be able to write some patterns more concisely, it would be nice if something like this were allowed:

match('a', 
      as('a').out('knows').as('b').out('knows').as('c'),
      as('c').out('knows').as('a')

which could be easily decomposed into the normalized form:

match('a', 
      as('a').out('knows').as('b'),
      as('b').out('knows').as('c'),
      as('c').out('knows').as('a')