Upstash Documentation

SPOP

Remove and return random members.
2 min read

Use SPOP to remove and return random members of a set.

Without a count one member is returned, or null when the key does not exist. With a count, up to that many distinct members are removed at once, capped at the size of the set, and the key is deleted when the last member is taken.

Since the read and the removal are atomic, no two callers can get the same member, which makes a set usable as a pool of unique items to hand out, such as invitation codes or shard assignments. Use SRANDMEMBER when the members should stay in the set.

Syntax#

Arguments#

ArgumentRequiredRepeatableDescription
<key>YesNoRedis key targeted by the command.
<count>NoNoNumber of members to pop.

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.

ProtocolReply
RESP2Null bulk string or null array, Bulk string, or array of bulk-string members
RESP3Null, Bulk string, or set of bulk-string members
Note

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.

Redis CLI
@upstash/redis
upstash_redis
ioredis
node-redis
redis-py
go-redis
jedis
redis-rs