You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2019/08/07 16:31:01 UTC
[jira] [Closed] (TINKERPOP-2133) Use neo4j index lookup in
Neo4jGraphStep with HasContainers containing TextP predicates
[ https://issues.apache.org/jira/browse/TINKERPOP-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-2133.
---------------------------------------
Resolution: Done
Assignee: stephen mallette
Fix Version/s: 3.5.0
> Use neo4j index lookup in Neo4jGraphStep with HasContainers containing TextP predicates
> ---------------------------------------------------------------------------------------
>
> Key: TINKERPOP-2133
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2133
> Project: TinkerPop
> Issue Type: Improvement
> Components: neo4j
> Affects Versions: 3.4.0
> Reporter: Andrey Skorikov
> Assignee: stephen mallette
> Priority: Trivial
> Fix For: 3.5.0
>
>
> When evaluating a Neo4jGraphStep with HasContainers containing TextP predicates, for example: g.V().has("Label", "name", TextP.containing("substring")), a scan over all vertices with the label is performed.
> Currently, an index lookup is used only when an complete property value is given, that is g.V().has("Label", "name", "exact") - implemented [here|https://github.com/apache/tinkerpop/blob/master/neo4j-gremlin/src/main/java/org/apache/tinkerpop/gremlin/neo4j/structure/trait/NoMultiNoMetaNeo4jTrait.java#L172].
> Allowing to use an index lookup for TextP predicates like containing, startingWith would substantially improve the evaluation performance.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)