[
https://issues.apache.org/jira/browse/TINKERPOP-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cole Greer closed TINKERPOP-1403.
---------------------------------
Fix Version/s: 3.7.0
3.5.7
3.6.5
Assignee: Cole Greer
Resolution: Fixed
Fixed in https://github.com/apache/tinkerpop/pull/2164
> 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
> Assignee: Cole Greer
> Priority: Major
> Labels: breaking
> Fix For: 3.7.0, 3.5.7, 3.6.5
>
>
> [~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
(v8.20.10#820010)
