Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

correction: AQL query results cache is only available on single servers #132

Merged
merged 1 commit into from
Aug 6, 2019
Merged

correction: AQL query results cache is only available on single servers #132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion 3.3/aql/execution-and-performance-query-cache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,11 @@ not many write queries.
The query cache is transparent so users do not need to manually invalidate
results in it if underlying collection data are modified.

{% hint 'info' %}
The AQL query results cache is only available for single servers, i.e. servers that
are not part of a cluster setup.
{% endhint %}


Modes
-----
Expand Down Expand Up @@ -55,7 +60,7 @@ executions of the same query.

A query is eligible for caching only if all of the following conditions are met:

* the server the query executes on is not a coordinator
* the server the query executes on is a single server (i.e. not part of a cluster)
* the query string is at least 8 characters long
* the query is a read-only query and does not modify data in any collection
* no warnings were produced while executing the query
Expand Down
7 changes: 6 additions & 1 deletion 3.4/aql/execution-and-performance-query-cache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,11 @@ not many write queries.
The query results cache is transparent so users do not need to manually invalidate
results in it if underlying collection data are modified.

{% hint 'info' %}
The AQL query results cache is only available for single servers, i.e. servers that
are not part of a cluster setup.
{% endhint %}


Modes
-----
Expand Down Expand Up @@ -55,7 +60,7 @@ executions of the same query.

A query is eligible for caching only if all of the following conditions are met:

* the server the query executes on is not a coordinator
* the server the query executes on is a single server (i.e. not part of a cluster)
* the query string is at least 8 characters long
* the query is a read-only query and does not modify data in any collection
* no warnings were produced while executing the query
Expand Down
7 changes: 6 additions & 1 deletion 3.5/aql/execution-and-performance-query-cache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,11 @@ not many write queries.
The query results cache is transparent so users do not need to manually invalidate
results in it if underlying collection data are modified.

{% hint 'info' %}
The AQL query results cache is only available for single servers, i.e. servers that
are not part of a cluster setup.
{% endhint %}


Modes
-----
Expand Down Expand Up @@ -55,7 +60,7 @@ executions of the same query.

A query is eligible for caching only if all of the following conditions are met:

* the server the query executes on is not a coordinator
* the server the query executes on is a single server (i.e. not part of a cluster)
* the query string is at least 8 characters long
* the query is a read-only query and does not modify data in any collection
* no warnings were produced while executing the query
Expand Down