Use ARMGET to read several array slots in one call.
The reply has one element per requested index, in the order the indexes were given, with null for an empty slot. That positional guarantee is what makes it usable as a gather step: the caller can zip the reply back onto its own list of indexes without re-checking which ones existed.
A key that does not exist behaves like an array where every slot is empty, so the reply is a list of nulls rather than an error.
See the array command overview for the data model these commands share.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Array key targeted by the command. |
<index> | Yes | Yes | Zero-based index to read. Repeat to read several slots in one call. |
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 | Array of bulk strings and null bulk strings |
| RESP3 | Array of bulk strings and nulls |
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.