1. 29 Dec, 2015 1 commit
  2. 18 Dec, 2015 1 commit
  3. 17 Dec, 2015 1 commit
    • antirez's avatar
      Cluster: resharding test now checks AOF consistency. · 9b4dd92c
      antirez authored
      It's a key invariant that when AOF is enabled, after the cluster
      reshards, a crash-recovery event causes all the keys to be still fine
      with the expected logical content. Now this is part of unit 04.
      9b4dd92c
  4. 11 Dec, 2015 2 commits
  5. 10 Dec, 2015 2 commits
    • antirez's avatar
      Cluster: more reliable migration tests. · 41db54a5
      antirez authored
      The old version was modeled with two failovers, however after the first
      it is possible that another slave will migrate to the new master, since
      for some time the new master is not backed by any slave. Probably there
      should be some pause after a failover, before the migration. Anyway the
      test is simpler in this way, and depends less on timing.
      41db54a5
    • antirez's avatar
      Cluster: more reliable replicas migration test. · b55affbc
      antirez authored
      b55affbc
  6. 28 Nov, 2015 1 commit
  7. 04 Nov, 2015 1 commit
  8. 03 Nov, 2015 1 commit
  9. 30 Oct, 2015 3 commits
  10. 15 Oct, 2015 1 commit
  11. 09 Oct, 2015 1 commit
  12. 07 Oct, 2015 1 commit
  13. 06 Oct, 2015 1 commit
  14. 01 Oct, 2015 2 commits
  15. 15 Sep, 2015 1 commit
    • antirez's avatar
      Test: fix false positive in HSTRLEN test. · 846da5b2
      antirez authored
      HINCRBY* tests later used the value "tmp" that was sometimes generated
      by the random key generation function. The result was ovewriting what
      Tcl expected to be inside Redis with another value, causing the next
      HSTRLEN test to fail.
      846da5b2
  16. 14 Sep, 2015 3 commits
    • antirez's avatar
      GEORADIUS: Don't report duplicates when radius is huge. · 3c23b5ff
      antirez authored
      Georadius works by computing the center + neighbors squares covering all
      the area of the specified position and radius. Then a distance filter is
      used to remove elements which are actually outside the range.
      
      When a huge radius is used, like 5000 km or more, adjacent neighbors may
      collide and be the same, leading to the reporting of the same element
      multiple times. This only happens in the edge case of huge radius but is
      not ideal.
      
      A robust but slow solution would involve qsorting the range to remove
      all the duplicates. However since the collisions are only in adjacent
      boxes, for the way they are ordered in the code, it is much faster to
      just check if the current box is the same as the previous one processed.
      
      This commit adds a regression test for the bug.
      
      Fixes #2767.
      3c23b5ff
    • antirez's avatar
      Test: MOVE expire test improved. · 0a91fc45
      antirez authored
      Related to #2765.
      0a91fc45
    • antirez's avatar
      MOVE now can move TTL metadata as well. · f529a01c
      antirez authored
      MOVE was not able to move the TTL: when a key was moved into a different
      database number, it became persistent like if PERSIST was used.
      
      In some incredible way (I guess almost nobody uses Redis MOVE) this bug
      remained unnoticed inside Redis internals for many years.
      Finally Andy Grunwald discovered it and opened an issue.
      
      This commit fixes the bug and adds a regression test.
      
      Close #2765.
      f529a01c
  17. 07 Sep, 2015 1 commit
    • antirez's avatar
      Test: print info on HSTRLEN test failure. · 467de61c
      antirez authored
      This additional info may provide more clues about the test randomly
      failing from time to time. Probably the failure is due to some previous
      test that overwrites the logical content in the Tcl variable, but this
      will make the problem more obvious.
      467de61c
  18. 05 Aug, 2015 3 commits
  19. 04 Aug, 2015 1 commit
  20. 09 Jul, 2015 1 commit
    • antirez's avatar
      GEOENCODE / GEODECODE commands removed. · b96af595
      antirez authored
      Rationale:
      
      1. The commands look like internals exposed without a real strong use
      case.
      2. Whatever there is an use case, the client would implement the
      commands client side instead of paying RTT just to use a simple to
      reimplement library.
      3. They add complexity to an otherwise quite straightforward API.
      
      So for now KILLED ;-)
      b96af595
  21. 29 Jun, 2015 4 commits
  22. 27 Jun, 2015 1 commit
  23. 26 Jun, 2015 1 commit
    • antirez's avatar
      Geo: from lat,lon API to lon,lat API according to GIS standard · fa9d62d3
      antirez authored
      The GIS standard and all the major DBs implementing GIS related
      functions take coordinates as x,y that is longitude,latitude.
      It was a bad start for Redis to do things differently, so even if this
      means that existing users of the Geo module will be required to change
      their code, Redis now conforms to the standard.
      
      Usually Redis is very backward compatible, but this is not an exception
      to this rule, since this is the first Geo implementation entering the
      official Redis source code. It is not wise to try to be backward
      compatible with code forks... :-)
      
      Close #2637.
      fa9d62d3
  24. 24 Jun, 2015 2 commits
    • antirez's avatar
      Geo: GEOHASH command test. · 5fd756bf
      antirez authored
      5fd756bf
    • antirez's avatar
      Geo: GEORADIUS fuzzy testing by reimplementing it in Tcl. · cf89a19f
      antirez authored
      We set random points in the world, pick a random position, and check if
      the returned points by Redis match the ones computed by Tcl by brute
      forcing all the points using the distance between two points formula.
      
      This approach is sounding since immediately resulted in finding a bug in
      the original implementation.
      cf89a19f
  25. 23 Jun, 2015 1 commit
  26. 22 Jun, 2015 2 commits