You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/08/10 14:38:20 UTC
[jira] [Created] (TINKERPOP-1403) Provide support for
GraphFilter.vertexProperties()
Marko A. Rodriguez created TINKERPOP-1403:
---------------------------------------------
Summary: Provide support for GraphFilter.vertexProperties()
Key: TINKERPOP-1403
URL: https://issues.apache.org/jira/browse/TINKERPOP-1403
Project: TinkerPop
Issue Type: Improvement
Components: process, structure
Affects Versions: 3.2.1
Reporter: Marko A. Rodriguez
Fix For: 3.3.0
[~rspitzer] stated that he is working with a graph that has millions of vertex properties on a vertex. If those properties are not needed for the traversal, then they should be filtered out.
Much like {{GraphFilter.edges()}}, we should add {{GraphFilter.vertexProperties(Traversal<Vertex,VertexProperty>)}}. That is, from the {{Vertex}} in question, traverse to those properties needed in the computation, where {{properties().limit(0)}} would be the push down predicate for "no properties." Another example, {{properties("income")}} would only provide income properties. Another example, {{properties("income").has("acl","public")}} would provide only those income properties that are public (according to access control).
--- SIDENOTE. In the docs we have {{bothE().limit(0)}} as the predicate for no edges. However, {{limit(0)}} by itself is sufficient. Likewise for {{GraphFilter.vertexProperties()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)