You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2017/02/10 21:54:41 UTC

[jira] [Updated] (TINKERPOP-1628) Implement TraversalSelectStep

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

Daniel Kuppitz updated TINKERPOP-1628:
--------------------------------------
    Description: 
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).

  was:
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}


> 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
>
> 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
(v6.3.15#6346)