DOC-723 | Query plan caching #641
Conversation
|
Deploy Preview Available Via |
| - `explainRegisters` (internal) | ||
| - `inaccessibleCollections` (internal) | ||
| - `shardIds` (internal) |
There was a problem hiding this comment.
Internal, correct?
site/content/3.12/aql/execution-and-performance/caching-query-plans.md
Outdated
Show resolved
Hide resolved
site/content/3.12/develop/http-api/queries/aql-query-plan-cache.md
Outdated
Show resolved
Hide resolved
site/content/3.12/release-notes/version-3.12/whats-new-in-3-12.md
Outdated
Show resolved
Hide resolved
| - An existing collection gets dropped or renamed, or the properties of an | ||
| existing collection are modified |
There was a problem hiding this comment.
But only if the affected collection is in the list of data sources for the cached query plan? At least that's what I saw. On the other hand, dropping a named graph with no collections in common, the cache did get cleared.
There was a problem hiding this comment.
If a named graph is changed or dropped, the complete cache for that database is eradicated. If a data source is changed, only those entries which are affected are deleted.
There was a problem hiding this comment.
Note to self: Check again whether the entire cache is now cleared on any of these events, including e.g. changing the schema, computed values, or cacheEnabled of a collection in single server.
There was a problem hiding this comment.
In single server, the cache isn't necessarily cleared entirely but it depends on the operation. I suggest we add a vague remark to the docs that operations may only remove affected entries in single server.
site/content/3.12/aql/execution-and-performance/caching-query-plans.md
Outdated
Show resolved
Hide resolved
| - An existing collection gets dropped or renamed, or the properties of an | ||
| existing collection are modified |
There was a problem hiding this comment.
If a named graph is changed or dropped, the complete cache for that database is eradicated. If a data source is changed, only those entries which are affected are deleted.
* Add query options to HTTP and JS API reference * Review, examples, adjust to changed behavior * Move (results) cache option to query sub options * Apply to 3.13
|
/generate-commit |
|
/generate-commit |
Partially apply changes to 3.11
|
/generate-commit |
Description
Upstream PRs