[jira] [Commented] (TINKERPOP-1764) Generalize MatchStep to localize all barriers, not just reducing barriers.

["Marko A. Rodriguez (JIRA)" <ji...@apache.org>]

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

Marko A. Rodriguez commented on TINKERPOP-1764:
-----------------------------------------------

{code}
gremlin> g.V().match(
......1>   __.as('a').outE('created').order().by('weight',decr).limit(1).inV().as('b'),
......2>   __.as('b').has('lang','java')
......3> ).select('a','b').by('name')
==>[a:marko,b:lop]
{code}

The question becomes, should this return 3 things?

{code}
marko,lop
peter,lop
josh,ripple
{code}

I believe so.

> Generalize MatchStep to localize all barriers, not just reducing barriers.
> --------------------------------------------------------------------------
>
>                 Key: TINKERPOP-1764
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1764
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.2.6
>            Reporter: Marko A. Rodriguez
>
> Given the semantics of order()/aggregate()/dedup(), this should work currently (perhaps), but I will make it explicit in MatchStep and provide test cases to ensure expected behavior. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)