[
https://issues.apache.org/jira/browse/TINKERPOP3-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532990#comment-14532990
]
Marko A. Rodriguez commented on TINKERPOP3-652:
-----------------------------------------------
I just pushed {{select(local)}}. It was trivial to implement. No duplication of
step code was needed. The drawback is now we have this:
{code}
g.V.out.match(...).select(local,'a','b')
{code}
I was thinking we can have an {{AutoScopeStrategy}} that basically realizes
that {{select}} is after a {{Map}} producing step and sets its scope to local.
Next, I think we can do the same thing for {{WhereStep}}. {{where(local)}} acts
on {{Map}} and {{where(global)}} acts on {{Path}}. The first we know, the
second, check it:
{code}
g.V.as('a').out('created').in('created').as('b').where('a',neq('b'))
{code}
No more {{ExceptStep}} !!!!!!
> select from Map should be explicit
> ----------------------------------
>
> Key: TINKERPOP3-652
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-652
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Matt Frantz
>
> Currently, {{select}} looks at the value in the traverser, and if it is a
> {{Map}}, it treats its arguments as keys, and extracts values from the
> {{Map}}. Otherwise, it treats its arguments as step labels and extracts
> values from the {{Path}}. It would seem less confusing to make this choice
> explicit.
> The two modes of {{select}} feel a bit like the two modes of {{range}}
> distinguished by the {{Scope}} parameter. Does {{select}} need a {{local}}
> option to make it expect a {{Map}}?
> Or would {{selectKeys}} be more consistent with {{hasKeys}}?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
