Skip to content

JSON.MGET - clarify behavior when the specified keys are in different shards #945

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.

Sign up for GitHub

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 3 commits into from
Dec 6, 2024
Merged

JSON.MGET - clarify behavior when the specified keys are in different shards #945

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8c7e2fb
Update index.md
LiorKogan Dec 4, 2024
ecccb2c
Update content/commands/json.mget/index.md
LiorKogan Dec 4, 2024
875bb89
Update index.md
LiorKogan Dec 5, 2024
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
4 changes: 4 additions & 0 deletions content/commands/json.mget/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,10 @@ Return the values at `path` from multiple `key` arguments

{{% warning %}}
When cluster mode is enabled, all specified keys must reside on the same [hash slot](https://redis.io/docs/latest/operate/oss_and_stack/reference/cluster-spec/#key-distribution-model).

When the database has more than one shard, and the specified keys reside in different shards, Redis will not report a CROSSSLOT error (to avoid breaking changes) and the results may be partial.


{{% /warning %}}

[Examples](#examples)
Expand Down
Loading