Sets the string value of a key, ignoring its type. The key is created if it doesn’t exist.
SET
key value [NX
| XX
] [GET
] [EX
seconds | PX
milliseconds | EXAT
unix-time-seconds | PXAT
unix-time-milliseconds | KEEPTTL
]
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.
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.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.
Any of the following:
Nil reply: GET
not given: Operation was aborted (conflict with one of the XX
/NX
options).
Simple string reply: OK
. GET
not given: The key was set.
Nil reply: GET
given: The key didn’t exist before the SET
.
Bulk string reply: GET
given: The previous value of the key.
Any of the following:
Null reply: GET
not given: Operation was aborted (conflict with one of the XX
/NX
options).
Simple string reply: OK
. GET
not given: The key was set.
Null reply: GET
given: The key didn’t exist before the SET
.
Bulk string reply: GET
given: The previous value of the key.
O(1)
@slow @string @write
127.0.0.1:6379> SET mykey "Hello"
OK
127.0.0.1:6379> GET mykey
"Hello"
127.0.0.1:6379>
127.0.0.1:6379> SET anotherkey "will expire in a minute" EX 60
OK
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:
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
EX
, PX
, NX
and XX
options.KEEPTTL
option.GET
, EXAT
and PXAT
option.NX
and GET
options to be used together.APPEND, DECR, DECRBY, GET, GETDEL, GETEX, GETRANGE, INCR, INCRBY, INCRBYFLOAT, LCS, MGET, MSET, MSETNX, SETRANGE, STRLEN.