[
https://issues.apache.org/jira/browse/TINKERPOP-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644855#comment-15644855
]
Marko A. Rodriguez commented on TINKERPOP-1541:
-----------------------------------------------
The only two steps that don't default to {{Pop.last}} are {{SelectOneStep}} and
{{SelectStep}}. I forced the to {{Pop.last}} default and only 6 test cases
failed (all contrived usages).
Wondering if for 3.3.0, we move to {{Pop.last}} default all around and add
{{selectV3d0()}} as the backwards compatibility update for users.
I suspect 99% of uses want {{Pop.last}} and it will allow us to do numerous
optimizations that we couldn't do before.
> Should repeated objects be returned for the same label?
> -------------------------------------------------------
>
> Key: TINKERPOP-1541
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1541
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.3
> Reporter: Marko A. Rodriguez
> Labels: breaking
>
> Check this out:
> {code}
> gremlin> g.V().as('a').select('a').as('a').select('a')
> ==>[v[1],v[1]]
> ==>[v[2],v[2]]
> ==>[v[3],v[3]]
> ==>[v[4],v[4]]
> ==>[v[5],v[5]]
> ==>[v[6],v[6]]
> {code}
> Shouldn't we just return the uniques? This is a big decision as this can
> cause massive rippling breakage for users :).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
