Why index is not applied?

[vitaliishandra]

We have index created with 'byAccountId2' with 'Enabled' status:

It works great when for example when we query the whole graph:

However for such query it didn't work:


The in step returns 300k vertexes.
If I remove filter by AccountId, everything is ok and query is executed immediately.
I tried to run REINDEX but it didn't help.
Any ideas how what can be wrong?

[porunov]

In your second query you are filtering by uid, but your byUid index is disabled. You need to enable index first before it can be used.

Also, graph indices are not applied after you are traversing from the initial filtered result.

Vertex centric indices can be used to filter connected edges in traversals when necessary, but in your case it won't help because you are filtering by adjacent vertices and not edges.

To filter result by adjacent vertex properties you may be interested in the next feature, but it's not implemented yet: #2287

[vitaliishandra]

Thank you for you answer. Regarding byUid - it is everything OK with it, as we have another index ENABLED byUniqueId.
Is it possible to somehow rewrite this query to apply index as now it took too long, beacuse first part returns ~300k vertexes: g.V().has('uid', within(...)).in("Direct", "Indirect") ?

[vitaliishandra]

@porunov Will vertex centric index will solve my issue in case I will move/duplciate property AccountId to Edge property: g.V().has('uid', within(...)).inE("Direct", "Indirect").has('AccountId', 257).out() ?

[porunov]

@porunov Will vertex centric index will solve my issue in case I will move/duplciate property AccountId to Edge property: g.V().has('uid', within(...)).inE("Direct", "Indirect").has('AccountId', 257).out() ?

Yes, in such case vertex centric index will be applied to your query