Use MSETNX to set several keys at once, but only if none of them already exists.
The command is all or nothing: if even a single key is present, nothing is written and the reply is 0; otherwise every key is written and the reply is 1. Since the check and the writes are one atomic step, it can be used to claim a whole group of related keys, so that a partially initialized state can never be observed.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> <value> | Yes | Yes | Key and the value to store in it. Repeat to set several keys 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 | Integer: 1 if all keys were set, 0 if no key was set |
| RESP3 | Integer: 1 if all keys were set, 0 if no key was set |
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.