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 2017/02/15 00:44:43 UTC

[jira] [Updated] (TINKERPOP-967) Support nested-repeat() structures

     [ https://issues.apache.org/jira/browse/TINKERPOP-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP-967:
---------------------------------------
    Fix Version/s:     (was: 3.2.4)
                   3.2.5

> Support nested-repeat() structures
> ----------------------------------
>
>                 Key: TINKERPOP-967
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-967
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.0-incubating
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>             Fix For: 3.2.5
>
>
> All the internal plumbing is staged for this to happen, we just haven't gone all the way. In short, a {{NESTED_LOOP}} traverser has an internal {{loopStack}} where {{repeat(repeat())}} will have a {{loopStack}} of two. The {{it.loops()}} checks of the internal repeat will always check the top of the stack and when its done repeating will delete its counter off the top of the stack.
> [~dkuppitz]'s work on {{LoopStep}} will be backwards compatible. In {{RepeatStep}} we will support:
> {code}
> repeat('a',out('knows').repeat('b',out('parent')))
> {code}
> and thus, things like {{loops('a')}} as well as {{times('a',2)}}. Note that naming the loop stack will be a super rare case as most people will just assume standard nested looping semantics with a push/pop stack.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)