Use COMMAND to get metadata about the commands the server supports, such as their arity, flags, and key positions. Client libraries call it during connection setup to discover how to route commands and where their keys are.
The current Upstash deployment accepts the command for client compatibility but returns an empty array rather than exposing the server command table, so clients fall back to their built-in command metadata.
Syntax#
Arguments#
This command takes no arguments.
Important points#
- The current Upstash deployment accepts
COMMANDfor client compatibility but returns an empty array; it does not expose the server command table.
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Empty array |
| RESP3 | Empty array |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
@upstash/redis
This command is not supported yet in @upstash/redis.
upstash_redis
This command is not supported yet in upstash_redis.