Package org.infinispan.server.resp.commands.set
package org.infinispan.server.resp.commands.set
-
ClassesClassDescriptionSADD implementation, see:invalid input: '{@link /*missing*/}' https://redis.io/commands/scard/ Returns the set cardinality (number of elements) of the set stored at key.invalid input: '{@link /*missing*/}' https://redis.io/commands/sdiff/ Returns the members of the set resulting from the difference between the first set and all the successive sets.invalid input: '{@link /*missing*/}' https://redis.io/commands/sdiffstore/invalid input: '{@link /*missing*/}' https://redis.io/commands/sinter/ Returns the members of the set resulting from the intersection of all the given sets.invalid input: '{@link /*missing*/}' https://redis.io/commands/sintercard/ Returns the cardinality of the resulting intersection set.invalid input: '{@link /*missing*/}' https://redis.io/commands/sinterstore/ This command is equal to SINTER, but instead of returning the resulting set, it is stored in destination.invalid input: '{@link /*missing*/}' https://redis.io/commands/sismember/ Returns 1 if element is member of the set stored at key, 0 otherwiseinvalid input: '{@link /*missing*/}' https://redis.io/commands/smembers/ Returns all the members of the set value stored at key.invalid input: '{@link /*missing*/}' https://redis.io/commands/smismember/SMOVE implementation, see: invalid input: '{@link /*missing*/}' https://redis.io/commands/smove/ Atomicity warning: Derogating to the above description, this implementation is not atomic: is it possible that, moving an existing element in source, at a given time a client can observe that element doesn't exists both in source and destination.SPOP implementation, see:SRANDMEMBER implementation, see:SREM implementation, see:`
SSCAN key cursor [MATCH pattern] [COUNT count]` command.SUNION implementation, see: invalid input: '{@link /*missing*/}' https://redis.io/commands/sunion/SUNIONSTORE implementation, see: invalid input: '{@link /*missing*/}' https://redis.io/commands/sunionstore/