SET · Valkey

SET

Sets the string value of a key, ignoring its type. The key is created if it doesn’t exist.

Usage

Description

Set key to hold the string value. If key already holds a value, it is overwritten, regardless of its type. Any previous time to live associated with the key is discarded on successful SET operation.

Options

The SET command supports a set of options that modify its behavior:

EX seconds – Set the specified expire time, in seconds (a positive integer).
PX milliseconds – Set the specified expire time, in milliseconds (a positive integer).
EXAT timestamp-seconds – Set the specified Unix time at which the key will expire, in seconds (a positive integer).
PXAT timestamp-milliseconds – Set the specified Unix time at which the key will expire, in milliseconds (a positive integer).
NX – Only set the key if it does not already exist.
XX – Only set the key if it already exists.
IFEQ comparison-value – Set the key if the comparison value matches the existing value. An error is returned and SET aborted if the value stored at key is not a string.
KEEPTTL – Retain the time to live associated with the key.
GET – Return the old string stored at key, or nil if key did not exist. An error is returned and SET aborted if the value stored at key is not a string.

Note: Since the SET command options can replace SETNX, SETEX, PSETEX, GETSET, it is possible that in future versions of Valkey these commands will be deprecated and finally removed.

Reply RESP2

If GET not given, any of the following:

Nil reply: Operation was aborted (conflict with one of the XX/NX options).
Simple string reply: OK: The key was set.

If GET given, any of the following:

Nil reply: The key didn’t exist before the SET.
Bulk string reply: The previous value of the key.

Note that when using GET together with XX/NX/IFEQ, the reply indirectly indicates whether the key was set:

GET and XX given: Non-Nil reply indicates the key was set.
GET and NX given: Nil reply indicates the key was set.
GET and IFEQ given: The key was set if the reply is equal to comparison-value.

Reply RESP3

If GET not given, any of the following:

Null reply: Operation was aborted (conflict with one of the XX/NX options).
Simple string reply: OK: The key was set.

If GET given, any of the following:

Null reply: The key didn’t exist before the SET.
Bulk string reply: The previous value of the key.

Note that when using GET together with XX/NX/IFEQ, the reply indirectly indicates whether the key was set:

GET and XX given: Non-Null reply indicates the key was set.
GET and NX given: Null reply indicates the key was set.
GET and IFEQ given: The key was set if the reply is equal to comparison-value.

Complexity

O(1)

ACL Categories

@slow @string @write

Examples

Basic usage

127.0.0.1:6379> SET mykey "Hello"
OK
127.0.0.1:6379> GET mykey
"Hello"

Set a value and an expiry time.

127.0.0.1:6379> SET anotherkey "will expire in a minute" EX 60
OK

Conditionally set a value.

127.0.0.1:6379> SET foo "Initial Value"
OK
127.0.0.1:6379> GET foo
"Initial Value"
127.0.0.1:6379> SET foo "New Value" IFEQ "Initial Value"
OK
127.0.0.1:6379> GET foo
"New Value"

Patterns

Note: The following pattern is discouraged in favor of the Redlock algorithm which is only a bit more complex to implement, but offers better guarantees and is fault tolerant.

The command SET resource-name anystring NX EX max-lock-time is a simple way to implement a locking system with Valkey.

A client can acquire the lock if the above command returns OK (or retry after some time if the command returns Nil), and remove the lock just using DEL.

The lock will be auto-released after the expire time is reached.

It is possible to make this system more robust modifying the unlock schema as follows:

Instead of setting a fixed string, set a non-guessable large random string, called token.
Instead of releasing the lock with DEL, send a script that only removes the key if the value matches.

This avoids that a client will try to release the lock after the expire time deleting the key created by another client that acquired the lock later.

An example of unlock script would be similar to the following:

if server.call("get",KEYS[1]) == ARGV[1]
then
    return server.call("del",KEYS[1])
else
    return 0
end

The script should be called with EVAL ...script... 1 resource-name token-value

History

1.0.0: Introduced.
2.6.12: Added the EX, PX, NX and XX options.
6.0.0: Added the KEEPTTL option.
6.2.0: Added the GET, EXAT and PXAT option.
7.0.0: Allowed the NX and GET options to be used together.
8.1.0: Added the IFEQ option.