
This is an attempt to normalize/formalize command summaries. Main actions performed: * Starts with the continuation of the phrase "The XXXX command, when called, ..." for user commands. * Starts with "An internal command...", "A container command...", etc... when applicable. * Always uses periods. * Refrains from referring to other commands. If this is needed, backquotes should be used for command names. * Tries to be very clear about the data type when applicable. * Tries to mention additional effects, e.g. "The key is created if it doesn't exist" and "The set is deleted if the last member is removed." * Prefers being terse over verbose. * Tries to be consistent.
37 lines
1005 B
JSON
37 lines
1005 B
JSON
{
|
|
"ADDSLOTSRANGE": {
|
|
"summary": "Assigns new hash slot ranges to a node.",
|
|
"complexity": "O(N) where N is the total number of the slots between the start slot and end slot arguments.",
|
|
"group": "cluster",
|
|
"since": "7.0.0",
|
|
"arity": -4,
|
|
"container": "CLUSTER",
|
|
"function": "clusterCommand",
|
|
"command_flags": [
|
|
"NO_ASYNC_LOADING",
|
|
"ADMIN",
|
|
"STALE"
|
|
],
|
|
"arguments": [
|
|
{
|
|
"name": "range",
|
|
"type": "block",
|
|
"multiple": true,
|
|
"arguments": [
|
|
{
|
|
"name": "start-slot",
|
|
"type": "integer"
|
|
},
|
|
{
|
|
"name": "end-slot",
|
|
"type": "integer"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"reply_schema": {
|
|
"const": "OK"
|
|
}
|
|
}
|
|
}
|