-
Notifications
You must be signed in to change notification settings - Fork 66
Multi-database support in cluster mode #242
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
base: main
Are you sure you want to change the base?
Conversation
- Updated documentation to reflect multi-database support in Valkey Cluster. - Removed outdated restrictions on `SELECT` and database-related commands. - Clarified that `MIGRATE`, `COUNTKEYSINSLOT`, and `GETKEYSINSLOT` operate within the selected database. - Clarified that `SWAPDB` is disabled in cluster mode to prevent shard inconsistencies. Signed-off-by: xbasel <[email protected]>
Depends on valkey-io/valkey#1671 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good, minor suggestions.
commands/cluster-countkeysinslot.md
Outdated
Returns the number of keys in the specified Valkey Cluster hash slot **in the | ||
currently selected database**. The command only queries the local data set, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need to bold the new text. I would clarify than when the default is 1, it captures all of the keys in the slot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@madolson
Could you clarify what you mean by when the default is 1, it captures all of the keys in the slot
?
commands/cluster-getkeysinslot.md
Outdated
The command returns an array of key names stored in the contacted node and | ||
hashing to the specified hash slot **in the currently selected database**. | ||
The maximum number of keys to return is specified via the `count` argument, | ||
so that it is possible for the user of this API to batch-process keys. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since you're here, can you clarify that batch processing only works if you are deleting the keys. If you are trying to scan the slot, you can't batch process it.
Also, I don't think we need to bold it's in the currently selected database.
Co-authored-by: Madelyn Olson <[email protected]> Signed-off-by: xbasel <[email protected]>
Co-authored-by: Madelyn Olson <[email protected]> Signed-off-by: xbasel <[email protected]>
Co-authored-by: Madelyn Olson <[email protected]> Signed-off-by: xbasel <[email protected]>
Signed-off-by: xbasel <[email protected]>
SELECT
and database-related commands.MIGRATE
,COUNTKEYSINSLOT
, andGETKEYSINSLOT
operate within the selected database.SWAPDB
is disabled in cluster mode to prevent shard inconsistencies.