optimizer should consider projections and stored values when selecting indexes about arangodb HOT 5 OPEN

is this OK?

from arangodb.

Thanks for reporting this issue.
Currently the optimizer will pick indexes based on how many attributes of the FILTER / SORT conditions are covered by an index, how selective an index is, and how many attributes it covers.
Unfortunately the stored values of an index are currently not taken into account during index selection. The same is true for attributes of documents that are used outside of FILTER / SORT conditions, which may be covered by indexes as well.
Right now the only workaround in this case is to manually add an index hint to the query as you did. Longer term, the optimizer will need to be changed so that it will also take into account which attributes of the collection/indexes are using by the query besides in the FILTER / SORT conditions.

from arangodb.

I'm turning this to a feature request, since we should eventually learn how to get this working without index hints.

from arangodb.

Please add the index definitions in question as well.

from arangodb.

Hi @jsteemann

OK, thanks for those clarifications.

from arangodb.