SET · Valkey

SET

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

Usage

SET key value [NX | XX] [GET] [EX seconds | PX milliseconds | EXAT unix-time-seconds | PXAT unix-time-milliseconds | KEEPTTL]

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:

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:

If GET given, any of the following:

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

Reply RESP3

If GET not given, any of the following:

If GET given, any of the following:

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

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:

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

See also

APPEND, DECR, DECRBY, GET, GETDEL, GETEX, GETRANGE, INCR, INCRBY, INCRBYFLOAT, LCS, MGET, MSET, MSETNX, SETRANGE, STRLEN.