- 02 Mar, 2016 1 commit
-
-
antirez authored
We want to report the original command in the stats, for example GEOADD, even when what is actually executed is the ZADD implementation.
-
- 29 Feb, 2016 1 commit
-
-
antirez authored
-
- 26 Feb, 2016 3 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
The new bitfield command is an extension to the Redis bit operations, where not just single bit operations are performed, but the array of bits composing a string, can be addressed at random, not aligned offsets, with any width unsigned and signed integers like u8, s5, u10 (up to 64 bit signed integers and 63 bit unsigned integers). The BITFIELD command supports subcommands that can SET, GET, or INCRBY those arbitrary bit counters, with multiple overflow semantics. Trivial and credits: A similar command was imagined a few times in the past, but for some reason looked a bit far fetched or not well specified. Finally the command was proposed again in a clear form by Yoav Steinberg from Redis Labs, that proposed a set of commands on arbitrary sized integers stored at bit offsets. Starting from this proposal I wrote an initial specification of a single command with sub-commands similar to what Yoav envisioned, using short names for types definitions, and adding control on the overflow. This commit is the resulting implementation. Examples: BITFIELD mykey OVERFLOW wrap INCRBY i2 10 -1 GET i2 10
-
- 19 Feb, 2016 1 commit
-
-
Salvatore Sanfilippo authored
Fixes double conversions in GEO
-
- 18 Feb, 2016 6 commits
-
-
Itamar Haber authored
-
Itamar Haber authored
-
Itamar Haber authored
-
antirez authored
Send a long double or double as a bulk reply, in a human friendly format.
-
antirez authored
-
antirez authored
Related to issue #3019.
-
- 17 Feb, 2016 1 commit
-
-
antirez authored
Now elements added to lists are incremental numbers in order to understand, when inconsistencies are found, what is the order in which the elements were added. Also the error now provides both the expected and found value.
-
- 15 Feb, 2016 1 commit
-
-
antirez authored
Close #3086.
-
- 10 Feb, 2016 2 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
cmsgpack: pass correct osize values to lua allocator
-
- 07 Feb, 2016 1 commit
-
-
yoav@monfort.co.il authored
-
- 05 Feb, 2016 1 commit
-
-
Salvatore Sanfilippo authored
Adds keyspace notifications for LREM
-
- 03 Feb, 2016 1 commit
-
-
Itamar Haber authored
-
- 02 Feb, 2016 4 commits
-
-
Itamar Haber authored
-
antirez authored
-
antirez authored
-
antirez authored
We need to be able to correctly parse the node address in the case of IPv6 addresses.
-
- 01 Feb, 2016 3 commits
- 29 Jan, 2016 9 commits
-
-
antirez authored
-
antirez authored
CLUSTER SLOTS now includes IDs in the nodes description associated with a given slot range. Certain client libraries implementations need a way to reference a node in an unique way, so they were relying on CLUSTER NODES, that is not a stable API and may change frequently depending on Redis Cluster future requirements.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 28 Jan, 2016 1 commit
-
-
antirez authored
-
- 27 Jan, 2016 2 commits
-
-
antirez authored
-
antirez authored
1. Bug #3035 is fixed (NULL pointer access). This was happening with the folling set of conditions: * For some reason one of the Sentinels, let's call it Sentinel_A, changed ID (reconfigured from scratch), but is as the same address at which it used to be. * Sentinel_A performs a failover and/or has a newer configuration compared to another Sentinel, that we call, Sentinel_B. * Sentinel_B receives an HELLO message from Sentinel_A, where the address and/or ID is mismatched, but it is reporting a newer configuration for the master they are both monitoring. 2. Sentinels now must have an ID otherwise they are not loaded nor persisted in the configuration. This allows to have conflicting Sentinels with the same address since now the master->sentinels dictionary is indexed by Sentinel ID. 3. The code now detects if a Sentinel is annoucing itself with an IP/port pair already busy (of another Sentinel). The old Sentinel that had the same port/pair is set as having port 0, that means, the address is invalid. We may discover the right address later via HELLO messages.
-
- 26 Jan, 2016 2 commits
-
-
antirez authored
Reported here: https://www.reddit.com/r/redis/comments/42r0i0/avg_ttl_varies_a_lot/
-
antirez authored
-