Skip to content

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

xbasel
Copy link
Member

@xbasel xbasel commented Mar 3, 2025

  • 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.

- 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]>
@xbasel xbasel self-assigned this Mar 3, 2025
@xbasel xbasel added the documentation Improvements or additions to documentation label Mar 3, 2025
@xbasel
Copy link
Member Author

xbasel commented Mar 3, 2025

Depends on valkey-io/valkey#1671
Fixes: valkey-io/valkey#1319

Copy link
Member

@madolson madolson left a 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.

Comment on lines 1 to 2
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,
Copy link
Member

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.

Copy link
Member Author

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?

Comment on lines 1 to 4
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.
Copy link
Member

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.

xbasel and others added 4 commits May 9, 2025 22:48
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants