Upstash Documentation

SINTER

Get set intersection.
2 min read

Use SINTER to get the members present in every one of the given sets.

A key that does not exist counts as an empty set, which makes the whole intersection empty. The result is computed on each call and not stored; use SINTERSTORE to keep it, or SINTERCARD when only the number of common members matters.

Intersections express "and" queries over sets, such as the users who are in both a campaign audience and a paying-customer set.

Syntax#

Arguments#

ArgumentRequiredRepeatableDescription
<key>YesYesRedis key targeted by the command.

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
RESP2Array of bulk-string members
RESP3Set 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