Use ARSCAN to list the occupied slots of an array in an index range.
Unlike ARGETRANGE, which returns a null for every hole, ARSCAN skips empty slots and pairs each value with its index, so the cost of the reply tracks the data actually stored rather than the width of the range. That is what makes it usable over a sparse array whose indexes are, for instance, timestamps.
Results come back in ascending index order. LIMIT caps how many slots are returned, so a scan over a wide range can be walked in pages by using the last index of one page as the start of the next.
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. |
<start> | Yes | No | First index of the range, inclusive. |
<end> | Yes | No | Last index of the range, inclusive. |
LIMIT <limit> | No | No | Maximum number of slots to return. Must be greater than 0. |
Important points#
- Only occupied slots are returned, in ascending index order.
<start>must not be greater than<end>; unlikeARGETRANGE,ARSCANdoes not reverse the range.
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 two-element arrays, each an index and its value |
| RESP3 | Array of two-element arrays, each an index and its value |
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.