Skip to content

Fix node-id type in cluster-setslot#10348

Merged
madolson merged 1 commit intoredis:unstablefrom
enjoy-binbin:fix_nodeid_type_in_setslot
Feb 28, 2022
Merged

Fix node-id type in cluster-setslot#10348
madolson merged 1 commit intoredis:unstablefrom
enjoy-binbin:fix_nodeid_type_in_setslot

Conversation

@enjoy-binbin
Copy link
Contributor

The type of node-id should be string, not integer.
Also improve the CLUSTER SETSLOT help message.

The type of node-id should be string, not integer.
Also improve the CLUSTER SETSLOT help message.
@enjoy-binbin enjoy-binbin added the state:to-be-merged The PR should be merged soon, even if not yet ready, this is used so that it won't be forgotten label Feb 27, 2022
Copy link
Contributor

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

All true

@madolson madolson merged commit ad7a627 into redis:unstable Feb 28, 2022
@enjoy-binbin enjoy-binbin deleted the fix_nodeid_type_in_setslot branch February 28, 2022 07:48
@enjoy-binbin
Copy link
Contributor Author

enjoy-binbin commented Mar 2, 2022

@madolson the time complexity should be O(N) ?
even in the old skiplist version, i think the log(N) also not very accurate.

{
"GETKEYSINSLOT": {
"summary": "Return local key names in the specified hash slot",
"complexity": "O(log(N)) where N is the number of requested keys",
"group": "cluster",
"since": "3.0.0",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:to-be-merged The PR should be merged soon, even if not yet ready, this is used so that it won't be forgotten

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants