You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/04/30 17:09:06 UTC

[jira] [Closed] (TINKERPOP3-649) no-arg select dynamic keys

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

Marko A. Rodriguez closed TINKERPOP3-649.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0.GA
         Assignee: Marko A. Rodriguez

Fixed. This also simplified the code a lot.

> no-arg select dynamic keys
> --------------------------
>
>                 Key: TINKERPOP3-649
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-649
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: Matt Frantz
>            Assignee: Marko A. Rodriguez
>             Fix For: 3.0.0.GA
>
>
> The currently implementation of the no-arg {{select}} form determines the set of labels via static analysis with {{TraversalHelper.getLabelsUpTo}}.  Instead, it should examine the {{Path}} and create a {{Map}} with keys for all labeled steps.
> Compare the current behavior of a 3-arg select on the modern graph:
> {noformat}
> gremlin> g.V().choose{it -> it.id()%3}
>   .option(0, __.as('x'))
>   .option(1, __.as('y'))
>   .option(2, __.as('z'))
>   .select('x', 'y', 'z')
> ==>[y:v[1]]
> ==>[z:v[2]]
> ==>[x:v[3]]
> ==>[y:v[4]]
> ==>[z:v[5]]
> ==>[x:v[6]]
> {noformat}
> The expected behavior of {{select()}} in place of {{select('x', 'y', 'z')}} would be the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)