[TINKERPOP-2528] Improve match() step to generate traversals that uses indexes

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.10
• Component/s: sparql
• Assignee: Unassigned
• Reporter: Marco Valzelli
• Created: 24/Feb/21 15:26
• Updated: 24/Feb/21 16:04

Description

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.