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

ASF GitHub Bot commented on TINKERPOP-1628:
-------------------------------------------

GitHub user dkuppitz opened a pull request:

    https://github.com/apache/tinkerpop/pull/844

    TINKERPOP-1628 Implement TraversalSelectStep

    https://issues.apache.org/jira/browse/TINKERPOP-1628
    
    This PR adds a `TraversalSelectStep` which supports the selection of 
dynamic / runtime-generated keys.
    
    `docker/build.sh -t -i -n` passed.
    
    VOTE: +1

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/tinkerpop TINKERPOP-1628

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tinkerpop/pull/844.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #844
    
----
commit 0028cf43e9f3c8af1bb2f619395b31dabafa5ffa
Author: Daniel Kuppitz <daniel_kuppitz@...>
Date:   2018-04-20T01:06:02Z

    TINKERPOP-1628 Implemented TraversalSelectStep

----


> Implement TraversalSelectStep
> -----------------------------
>
>                 Key: TINKERPOP-1628
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1628
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.3.0
>            Reporter: Daniel Kuppitz
>            Assignee: Daniel Kuppitz
>            Priority: Major
>
> It should be possible to have nested {{select()}} or rather to select dynamic 
> keys.
> {noformat}
> gremlin> aliases = ["marko":"okram"]
> gremlin> g.withSideEffect("a", aliases).V().hasLabel("person").
>            values("name").as("n").
>            optional(select("a").select(select("n")))
> ==>okram
> ==>vadas
> ==>josh
> ==>peter
> {noformat}
> I know there are more steps that could / should allow traversals, but to me 
> {{select()}} seems to be the most important one (perhaps because the 
> workaround is / can be super expensive).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to