[
https://issues.apache.org/jira/browse/TINKERPOP-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086557#comment-15086557
]
Marko A. Rodriguez commented on TINKERPOP-736:
----------------------------------------------
Given the amount of work for 3.1.1 and 3.2.0, I have removed the "fix version"
for this issue. It is not a bug so we can add it later.
> Automatic Traversal rewriting
> -----------------------------
>
> Key: TINKERPOP-736
> URL: https://issues.apache.org/jira/browse/TINKERPOP-736
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.2-incubating
> Reporter: Matthias Broecheler
> Assignee: Marko A. Rodriguez
> Priority: Minor
>
> 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:
> {code}
> match('a',
> as('a').out('knows').as('b').out('knows').as('c'),
> as('c').out('knows').as('a')
> {code}
> which could be easily decomposed into the normalized form:
> {code}
> match('a',
> as('a').out('knows').as('b'),
> as('b').out('knows').as('c'),
> as('c').out('knows').as('a')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
