Daniel Kuppitz created TINKERPOP3-774:
-----------------------------------------
Summary: order / dedup issues
Key: TINKERPOP3-774
URL: https://issues.apache.org/jira/browse/TINKERPOP3-774
Project: TinkerPop 3
Issue Type: Bug
Components: process
Affects Versions: 3.0.0-incubating
Reporter: Daniel Kuppitz
Assignee: Marko A. Rodriguez
Not sure if this is an {{order}}- or a {{dedup}}-issue (or maybe both), but
these two steps don't play well together. The following sample were created
using the GD graph.
*{{dedup()}} w/o keys*
{code}
g.V().as("a").outE("followedBy").as("e").inV().as("b").
select("e").order().by("weight", decr).limit(10).
select("b").out("sungBy").dedup()
==>v[453]
==>v[347]
==>v[405]
==>v[342]
==>v[342]
==>v[340]
==>v[342]
==>v[351]
==>v[351]
{code}
*{{dedup()}} w/ keys*
{code}
g.V().as("a").outE().as("e").inV().as("b").
select("e").order().by("weight", decr).limit(10).
as("c").inV().as("d").dedup("c","d")
Neither the sideEffects, map, nor path has a c-key: DedupGlobalStep([c, d])
Display stack trace? [yN]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
