tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TINKERPOP-967) Support nested-repeat() structures
Date Mon, 25 Jun 2018 19:31:00 GMT

    [ https://issues.apache.org/jira/browse/TINKERPOP-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522716#comment-16522716

ASF GitHub Bot commented on TINKERPOP-967:

Github user dkuppitz commented on the issue:

    I agree it should be treated differently. Since `as()` labeling has an impact on the path
history, it really shouldn't be used for this case.

> 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
>            Priority: Major
> 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

View raw message