Matt Frantz created TINKERPOP3-779:
--------------------------------------
Summary: coalesce should not forget path
Key: TINKERPOP3-779
URL: https://issues.apache.org/jira/browse/TINKERPOP3-779
Project: TinkerPop 3
Issue Type: Bug
Components: process
Affects Versions: 3.0.0-incubating
Reporter: Matt Frantz
Assignee: Marko A. Rodriguez
It seems like the path along whichever branch of the {{coalesce}} step should
be preserved downstream. In 3.0.0, this is not the case:
{noformat}
gremlin> g.V().out().out().path()
==>[v[1], v[4], v[5]]
==>[v[1], v[4], v[3]]
gremlin> g.V().coalesce(out().out()).path()
==>[v[1], v[5]]
==>[v[1], v[3]]
{noformat}
I would expect the output of the second statement to equal the first.
Also, to be clear, the path should reflect whichever of the traversal arguments
to {{coalesce}} were productive.
{noformat}
gremlin> g.V().out().out().path()
==>[v[1], v[4], v[5]]
==>[v[1], v[4], v[3]]
gremlin> g.V().coalesce(out().out().out(), out().out()).path()
==>[v[1], v[5]]
==>[v[1], v[3]]
{noformat}
Again, I would expect the output of the second statement to equal the first.
The path truncation behavior would be nice to preserve in the proposed {{sub}}
step (TINKERPOP3-716).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
