--- acl_categories: - '@write' - '@sortedset' - '@fast' arguments: - display_text: key key_spec_index: 0 name: key type: key - arguments: - display_text: nx name: nx token: NX type: pure-token - display_text: xx name: xx token: XX type: pure-token name: condition optional: true since: 3.0.2 type: oneof - arguments: - display_text: gt name: gt token: GT type: pure-token - display_text: lt name: lt token: LT type: pure-token name: comparison optional: true since: 6.2.0 type: oneof - display_text: change name: change optional: true since: 3.0.2 token: CH type: pure-token - display_text: increment name: increment optional: true since: 3.0.2 token: INCR type: pure-token - arguments: - display_text: score name: score type: double - display_text: member name: member type: string multiple: true name: data type: block arity: -4 categories: - docs - develop - stack - oss - rs - rc - oss - kubernetes - clients command_flags: - write - denyoom - fast complexity: O(log(N)) for each item added, where N is the number of elements in the sorted set. description: Adds one or more members to a sorted set, or updates their scores. Creates the key if it doesn't exist. group: sorted-set hidden: false history: - - 2.4.0 - Accepts multiple elements. - - 3.0.2 - Added the `XX`, `NX`, `CH` and `INCR` options. - - 6.2.0 - Added the `GT` and `LT` options. key_specs: - RW: true begin_search: spec: index: 1 type: index find_keys: spec: keystep: 1 lastkey: 0 limit: 0 type: range update: true linkTitle: ZADD railroad_diagram: /images/railroad/zadd.svg since: 1.2.0 summary: Adds one or more members to a sorted set, or updates their scores. Creates the key if it doesn't exist. syntax_fmt: "ZADD key [NX | XX] [GT | LT] [CH] [INCR] score member [score member\n\ \ ...]" title: ZADD --- Adds all the specified members with the specified scores to the sorted set stored at `key`. It is possible to specify multiple score / member pairs. If a specified member is already a member of the sorted set, the score is updated and the element reinserted at the right position to ensure the correct ordering. If `key` does not exist, a new sorted set with the specified members as sole members is created, like if the sorted set was empty. If the key exists but does not hold a sorted set, an error is returned. The score values should be the string representation of a double precision floating point number. `+inf` and `-inf` values are valid values as well. ZADD options --- ZADD supports a list of options, specified after the name of the key and before the first score argument. Options are: * **XX**: Only update elements that already exist. Don't add new elements. * **NX**: Only add new elements. Don't update already existing elements. * **LT**: Only update existing elements if the new score is **less than** the current score. This flag doesn't prevent adding new elements. * **GT**: Only update existing elements if the new score is **greater than** the current score. This flag doesn't prevent adding new elements. * **CH**: Modify the return value from the number of new elements added, to the total number of elements changed (CH is an abbreviation of *changed*). Changed elements are **new elements added** and elements already existing for which **the score was updated**. So elements specified in the command line having the same score as they had in the past are not counted. Note: normally the return value of `ZADD` only counts the number of new elements added. * **INCR**: When this option is specified `ZADD` acts like [`ZINCRBY`]({{< relref "/commands/zincrby" >}}). Only one score-element pair can be specified in this mode. Note: The **GT**, **LT** and **NX** options are mutually exclusive. Range of integer scores that can be expressed precisely --- Redis sorted sets use a *double 64-bit floating point number* to represent the score. In all the architectures we support, this is represented as an **IEEE 754 floating point number**, that is able to represent precisely integer numbers between `-(2^53)` and `+(2^53)` included. In more practical terms, all the integers between -9007199254740992 and 9007199254740992 are perfectly representable. Larger integers, or fractions, are internally represented in exponential form, so it is possible that you get only an approximation of the decimal number, or of the very big integer, that you set as score. Sorted sets 101 --- Sorted sets are sorted by their score in an ascending way. The same element only exists a single time, no repeated elements are permitted. The score can be modified both by `ZADD` that will update the element score, and as a side effect, its position on the sorted set, and by [`ZINCRBY`]({{< relref "/commands/zincrby" >}}) that can be used in order to update the score relatively to its previous value. The current score of an element can be retrieved using the [`ZSCORE`]({{< relref "/commands/zscore" >}}) command, that can also be used to verify if an element already exists or not. For an introduction to sorted sets, see the data types page on [sorted sets][tdtss]. [tdtss]: /develop/data-types#sorted-sets Elements with the same score --- While the same element can't be repeated in a sorted set since every element is unique, it is possible to add multiple different elements *having the same score*. When multiple elements have the same score, they are *ordered lexicographically* (they are still ordered by score as a first key, however, locally, all the elements with the same score are relatively ordered lexicographically). The lexicographic ordering used is binary, it compares strings as array of bytes. If the user inserts all the elements in a sorted set with the same score (for example 0), all the elements of the sorted set are sorted lexicographically, and range queries on elements are possible using the command [`ZRANGEBYLEX`]({{< relref "/commands/zrangebylex" >}}) (Note: it is also possible to query sorted sets by range of scores using [`ZRANGEBYSCORE`]({{< relref "/commands/zrangebyscore" >}})). ## Examples {{< clients-example set="cmds_sorted_set" step="zadd" description="Foundational: Add one or more members to a sorted set with scores using ZADD (creates sorted set if needed, updates scores if member exists)" difficulty="beginner" >}} > ZADD myzset 1 "one" (integer) 1 > ZADD myzset 1 "uno" (integer) 1 > ZADD myzset 2 "two" 3 "three" (integer) 2 > ZRANGE myzset 0 -1 WITHSCORES 1) "one" 2) "1" 3) "uno" 4) "1" 5) "two" 6) "2" 7) "three" 8) "3" {{< /clients-example >}} Give these commands a try in the interactive console: {{% redis-cli %}} ZADD myzset 1 "one" ZADD myzset 1 "uno" ZADD myzset 2 "two" 3 "three" ZRANGE myzset 0 -1 WITHSCORES {{% /redis-cli %}} ## Redis Software and Redis Cloud compatibility | Redis
Software | Redis
Cloud | Notes | |:----------------------|:-----------------|:------| | ✅ Standard
✅ Active-Active | ✅ Standard
✅ Active-Active | | ## Return information {{< multitabs id="zadd-return-info" tab1="RESP2" tab2="RESP3" >}} Any of the following: * [Nil reply](../../develop/reference/protocol-spec#bulk-strings): if the operation was aborted because of a conflict with one of the _XX/NX/LT/GT_ options. * [Integer reply](../../develop/reference/protocol-spec#integers): the number of new members when the _CH_ option is not used. * [Integer reply](../../develop/reference/protocol-spec#integers): the number of new or updated members when the _CH_ option is used. * [Bulk string reply](../../develop/reference/protocol-spec#bulk-strings): the updated score of the member when the _INCR_ option is used. -tab-sep- Any of the following: * [Null reply](../../develop/reference/protocol-spec#nulls): if the operation was aborted because of a conflict with one of the _XX/NX/LT/GT_ options. * [Integer reply](../../develop/reference/protocol-spec#integers): the number of new members when the _CH_ option is not used. * [Integer reply](../../develop/reference/protocol-spec#integers): the number of new or updated members when the _CH_ option is used. * [Double reply](../../develop/reference/protocol-spec#doubles): the updated score of the member when the _INCR_ option is used. {{< /multitabs >}}