Use HSETNX to set a hash field only when it does not already exist.
The reply is 1 when the field was created and 0 when it was already present and left untouched. The check and the write happen atomically, so of several clients racing to fill the same field exactly one succeeds, which makes the command a way to claim a slot inside a hash without overwriting whatever a concurrent writer put there.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<field> | Yes | No | Hash field name. |
<value> | Yes | No | Value to store in the field. |
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 the field was set, 0 if it already exists |
| RESP3 | Integer: 1 if the field was set, 0 if it already exists |
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.