Module table 

The command table: what each command is called, how many arguments it takes, where its keys are, and what COMMAND reports about it.

Every field here was read out of a running Redis 8.8 with COMMAND INFO rather than written from the documentation, because this is the table a client library builds its own routing from. A cluster aware client asks COMMAND where the keys are and then decides which node to send a command to, so an arity or a key position that is off by one does not produce a wrong error message, it produces a client that sends MSET to the wrong shard. The summaries are ours, since those are the one field nobody parses.

cargo xtask check compares this table against commands.toml in both directions, so a command cannot be dispatched without a storage plan and cannot claim wire = "verified" without an entry here.

Structs

Spec

Everything COMMAND has to be able to say about one command.

Statics

COMMANDS

Every command this server answers, in the order the groups ship.

Functions

arity_ok

Whether n arguments, counting the name, satisfy this command’s arity.

lookup

The command called name, whatever case the client spelled it in.