- 13 Jan, 2017 2 commits
-
-
Jan-Erik Rediger authored
-
antirez authored
As suggested by @itamarhaber.
-
- 12 Jan, 2017 11 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
As a side effect of supporting it, we no longer crash when MEMORY USAGE is called against a module data type. Close #3637.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Don't go over 80 cols. Start with captial letter, capital letter afer point, end comment with a point and so forth. No actual code behavior touched at all.
-
antirez authored
This commit also includes minor aesthetic changes like removal of trailing spaces.
-
oranagra authored
-
oranagra authored
-
- 21 Dec, 2016 4 commits
-
-
antirez authored
Close #3687.
-
antirez authored
-
Alexander Zhukov authored
-
whatacold authored
-
- 20 Dec, 2016 7 commits
-
-
antirez authored
-
antirez authored
We need to report all the points added into the set, not just the ones matching the Tcl distance algo.
-
antirez authored
The same thing observed in #3551 by gnethercutt also fixed for GEOHASH as the original PR did.
-
antirez authored
There were two cases outlined in issue #3512 and PR #3551 where the Geo API returned unexpected results: empty strings where NULL replies were expected, or a single null reply where an array was expected. This violates the Redis principle that Redis replies for existing keys or elements should be indistinguishable. This is technically an API breakage so will be merged only into 4.0 and specified in the changelog in the list of breaking compatibilities, even if it is not very likely that actual code will be affected, hopefully, since with the past behavior basically there was to acconut for *both* the possibilities, and the new behavior is always one of the two, but in a consistent way.
-
Justin Carvalho authored
-
antirez authored
-
antirez authored
You can still force the logo in the normal logs. For motivations, check issue #3112. For me the reason is that actually the logo is nice to have in interactive sessions, but inside the logs kinda loses its usefulness, but for the ability of users to recognize restarts easily: for this reason the new startup sequence shows a one liner ASCII "wave" so that there is still a bit of visual clue. Startup logging was modified in order to log events in more obvious ways, and to log more events. Also certain important informations are now more easy to parse/grep since they are printed in field=value style. The option --always-show-logo in redis.conf was added, defaulting to no.
-
- 19 Dec, 2016 7 commits
-
-
antirez authored
-
antirez authored
This commit also contains other changes in order to conform the code to the Redis core style, specifically 80 chars max per line, smart conditionals in the same line: if (that) do_this();
-
itamar authored
-
andyli authored
-
oranagra authored
when a slave loads an RDB, stop an AOFRW fork before flusing db and parsing rdb file, to avoid a CoW disaster.
-
hylepo authored
Fixing typo in the usage of redis-benchmark
-
oranagra authored
-
- 16 Dec, 2016 7 commits
-
-
antirez authored
The new algorithm provides the same speed with a smaller error for cardinalities in the range 0-100k. Before switching, the new and old algorithm behavior was studied in details in the context of issue #3677. You can find a few graphs and motivations there.
-
antirez authored
Otherwise for small cardinalities the algorithm will output something like, for example, 4.99 for a candinality of 5, that will be converted to 4 producing a huge error.
-
antirez authored
The PFADD now takes an array and has mandatory two arguments.
-
Harish Murthy authored
Config option to use LogLog-Beta Algorithm for Cardinality
-
Dvir Volk authored
-
antirez authored
-
antirez authored
The commit improves ziplistRepr() and adds a new debugging subcommand so that we can trigger the dump directly from the Redis API. This command capability was used while investigating issue #3684.
-
- 14 Dec, 2016 2 commits
-
-
antirez authored
After the fix for #3673 the ttl var is always initialized inside the loop itself, so the early initialization is not needed. Variables declaration also moved to a more local scope.
-
Jan-Erik Rediger authored
Before, if a previous key had a TTL set but the current one didn't, the TTL was reused and thus resulted in wrong expirations set. This behaviour was experienced, when `MigrateDefaultPipeline` in redis-trib was set to >1 Fixes #3655
-