mirror of https://gitee.com/bigwinds/arangodb
792f57b760
When an "outbound" query is made with the paths() function, the optimiser will now use an index if a FILTER condition can exploit an index on .source. Example query: FOR p IN PATHS(users, relations, "outbound") FILTER p.source._id == "some-id" RETURN p The index on p._id was not exploited before, because the optimiser did not know that variable "p" related to collection "users" and that the condition actually would filter on users._id (the variable name in the FILTER statement is "p.source._id). Now, AQL functions can define callbacks which are called by the optimiser to try some function-specific optimisations. The optimise callback for PATHS() tries to exploit indexes for filters that filter on the vertex collection (1st parameter to PATHS() call). Indexes can be exploited if the query is an "outbound" query and there are filters on "source", or if the query is an "inbound" query and there are filters on "destination". "anybound" queries will not be optimised |
||
|---|---|---|
| .. | ||
| modules | ||
| tests | ||
| ahuacatl.js | ||
| arango-dfdb.js | ||
| arango-password.js | ||
| arango-upgrade.js | ||
| server.js | ||