Jan

@matcho : I remember there were issues with index hints in some specific situations, which were fixed a while ago. I guess if you are running the queries on ArangoDB...

@matcho : thanks for reporting back. I also checked our code and found that there are just 2 optimizer rules which will create additional plans: the one you mentioned and...

For info, I created a PR that can reduce the number of plans generated by the optimizer rule "interchange-adjacent-enumerations" in some cases: https://github.com/arangodb/arangodb/pull/20201 For the example query provided in this...

As we don't want to change the defaults or behavior for the 3.11 stable branch too much, we will go ahead with the above change (https://github.com/arangodb/arangodb/pull/20201) only from 3.12 onwards....

Adopted by @alexbakharew.

Original issue is still unfixed. PR may be reopened later when the issue gets fixed.

@matcho : I will have a look at the issue today

I created the following dataset for the analysis: ``` c = db._create("z_obs"); docs = []; for (i = 0; i < 3500000; ++i) { docs.push({ _key: "test" + i, date_created:...

@matcho : your suggestion to split up the query into 3 different lookup subqueries, each with a limit, and then joining their results for getting the data back in total...

Consider the following original query ``` FOR v, e, path IN 0..1 outbound 'nodes/2' edges FILTER e._to == 'nodes/td_0' RETURN v._key ``` This is a traversal that looks for all...