[
https://issues.apache.org/jira/browse/TINKERPOP-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette updated TINKERPOP-2528:
----------------------------------------
Component/s: (was: translator)
sparql
Flags: (was: Important)
Issue Type: Improvement (was: Bug)
Labels: (was: index match sparql)
> Improve match() step to generate traversals that uses indexes
> -------------------------------------------------------------
>
> Key: TINKERPOP-2528
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2528
> Project: TinkerPop
> Issue Type: Improvement
> Components: sparql
> Affects Versions: 3.4.10
> Reporter: Marco Valzelli
> Priority: Major
>
> Within this issue:
> https://issues.apache.org/jira/browse/TINKERPOP-2325
> it has been tried to fix the behavior of the SPARQL component, to generate
> traversals that uses the defined indexes.
> In this issue's discussion it became clear that the real fix was deeper, in
> the match() step.
> In fact [~spmallette] in the github thread wrote:
> "It made me wonder if we should try to simply optimize {{match()}} better so
> that it gives providers a better chance at using an index...in that way we
> get improvements to {{match()}} for native usage and to sparql-gremlin and
> other language compilers. As I mentioned previously, we'll create new JIRA
> issues as needed for these improvements going forward."
> ([https://github.com/apache/tinkerpop/pull/1237#issuecomment-580747001)]
> So I open this issue to ask for the implementation of this improvements to
> the {{match()}} step, for native usage, sparql-gremlin component and other
> language compilers.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
