Use BITFIELD_RO to read one or more bitfield values without modifying the key.
It is the read-only form of BITFIELD and accepts GET operations only, so it is safe to run on replicas and from read-only scripts. Each GET names an encoding, u<bits> for unsigned or i<bits> for signed integers, and a bit offset that can be written as #<n> to address the n-th field of that width. The reply holds one integer per GET, and any part of a field that lies past the end of the stored string reads as zero.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
GET <encoding> <offset> | No | Yes | Read the value at <offset> using <encoding>, such as u8 or i16. Repeat to read several fields. |
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 integer or null replies, one per subcommand |
| RESP3 | Array of integer or null replies, one per subcommand |
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.