[
https://issues.apache.org/jira/browse/TINKERPOP-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841634#comment-16841634
]
Daniel Choi commented on TINKERPOP-2220:
----------------------------------------
[~okram] could you chime in on this? The explanation in the 524 pull request
above seems to imply there context carry over is intended between iterations,
but that feels like to me it's breaking the "barrier" nature of dedup(). The
second dedup() is reaching into the first dedup()'s context (the deduping set),
breaking the barrier, so to speak.
> Dedup inside Repeat Produces 0 results
> --------------------------------------
>
> Key: TINKERPOP-2220
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2220
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.3.0
> Reporter: Rahul Chander
> Priority: Major
>
> Testing against the Tinkerpop Modern graph dataset, I ran this query:
> {code:java}
> g.V().repeat(__.dedup()).times(2).count()
> {code}
> which should essentially be the same as running dedup twice. It produced 0
> results, while dedup twice produced the correct 6.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
