Marko A. Rodriguez created TINKERPOP3-681:
---------------------------------------------
Summary: SubgraphStrategy should use traversal, not lambdas for
filtering
Key: TINKERPOP3-681
URL: https://issues.apache.org/jira/browse/TINKERPOP3-681
Project: TinkerPop 3
Issue Type: Bug
Components: process
Reporter: Marko A. Rodriguez
Assignee: stephen mallette
Fix For: 3.0.0.GA
{{SubgraphStrategy}} should use {{Traversal}} to determine if a vertex/edge
should exist in the projection. See {{TraversalUtil.test(object,traversal)}}
which simply returns true or false if the {{traversal.hasNext()}}. It also
auto-resets the traversal, etc. Thus, simple dimple.
If a user does want to use a lambda, well, then their traversal is:
{code}
__.filter{ // mylambda }}
{code}
This will allow {{SubgraphStrategy}} to work in OLAP as well as be consistent
with the Gremlin pattern -- no lambdas. If you use a lambda, its in a
{{Traversal}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
