[
https://issues.apache.org/jira/browse/TINKERPOP3-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632591#comment-14632591
]
Marko A. Rodriguez commented on TINKERPOP3-774:
-----------------------------------------------
I think the "filter ranking" should be this:
{code}
is(predicate)
has(predicate)
where(predicate)
simplePath()
cyclicPath()
filter(traversal)
has(traversal)
where(traversal)
or(...)
and(...)
dedup()
order()
{code}
We have to think what role {{as()}} plays here. Especially with nested
traversals that might contain a {{select}}.
I would say the algorithm is to isolate a sequence of steps that are in the
above selection and then {{Comparator<Step>}} and reinsert them back into the
traversal. Easy peasy.
> 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: Daniel Kuppitz
>
> 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)
