8000 prototype for forceOneShardAttributeValue by jsteemann · Pull Request #14701 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

prototype for forceOneShardAttributeValue #14701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Sep 7, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
changelog
  • Loading branch information
hkernbach committed Sep 6, 2021
commit 595fce7ce4679eb2a2efbd9a0d30bab8541f35f0
10 changes: 10 additions & 0 deletions CHANGELOG
Original file line number Diff line number Diff line change
@@ -1,6 +1,16 @@
devel
-----

* (EE only) Bug-fix: If you created a ArangoSearch view on Satellite-
Collections only and then join with a collection only having a single
shard the cluster-one-shard-rule was falsly applied and could lead to
empty view results. The Rule will now detect the situation properly,
and not trigger.

* (EE only) If you have a query using only satellite collections,
now the cluster-one-shard-rule can be applied to improve
query performance.

* (Enterprise Edition only): added query option `forceOneShardAttributeValue`
to explicitly set a shard key value that will be used during query snippet
distribution to limit the query to a specific server in the cluster.
Expand Down
0