You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/10/16 17:56:05 UTC
[jira] [Updated] (TINKERPOP3-736) Automatic Traversal rewriting
[ https://issues.apache.org/jira/browse/TINKERPOP3-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette updated TINKERPOP3-736:
----------------------------------------
Priority: Minor (was: Trivial)
> Automatic Traversal rewriting
> -----------------------------
>
> Key: TINKERPOP3-736
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-736
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.1-incubating
> Reporter: Matthias Broecheler
> 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)