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 2015/03/27 22:02:53 UTC
[jira] [Closed] (TINKERPOP3-589) Using a strategy graph prevents
underlying neo4j indices to be used.
[ https://issues.apache.org/jira/browse/TINKERPOP3-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP3-589.
---------------------------------------
Resolution: Won't Fix
Fix Version/s: 3.0.0.GA
This issue won't be directly fixed as {{GraphStrategy}} has been replaced by {{TraversalStrategy}}. All strategies will be developed within the context of a {{Traversal}} which simplifies the boilerplate even beyond what {{GraphStrategy}} did for TP2 "wrapppers". The limitation of course is that {{TraversalStrategy}} only applies to `Traversal` objects so you can't really add functionality at the `Graph` level. If someone needs to to do that they will need to build custom wrappers (which tends to get complicated, at least insofar as trying to provide a generalized approach to them....maybe easier to do in a specific domain, but i'm not completely clear on that).
> Using a strategy graph prevents underlying neo4j indices to be used.
> --------------------------------------------------------------------
>
> Key: TINKERPOP3-589
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-589
> Project: TinkerPop 3
> Issue Type: Bug
> Components: neo4j, structure
> Reporter: dlorange
> Priority: Critical
> Fix For: 3.0.0.GA
>
>
> Using tinkerpop3 M7, I've found that applying any GraphStrategy to a Neo4jGraph prevents the underlying neo4j indices to be used.
> Are there any known workarounds for this issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)