This uses commands.json from redis's documentation to determine which
category a given redis command falls into.
This will be useful to ensure that twemproxy stays up to date with new redis
commands. (but the new script still requires a lot of manual work).
This was used to generate the previously added documentation and determine which redis commands to add where.
Problem
It's difficult to manually track which redis commands have which key/argument counts for dozens of commands
Solution
Track this in a script which will output information about any missing or out of date redis command argument info.
This uses commands.json from redis's documentation to determine which category a given redis command falls into. This will be useful to ensure that twemproxy stays up to date with new redis commands. (but the new script still requires a lot of manual work).
This was used to generate the previously added documentation and determine which redis commands to add where.
Problem
It's difficult to manually track which redis commands have which key/argument counts for dozens of commands
Solution
Track this in a script which will output information about any missing or out of date redis command argument info.