1. 09 Oct, 2018 4 commits
  2. 03 Oct, 2018 5 commits
  3. 29 Aug, 2018 3 commits
  4. 02 Aug, 2018 3 commits
  5. 30 Jul, 2018 1 commit
  6. 24 Jul, 2018 2 commits
  7. 23 Jul, 2018 1 commit
    • antirez's avatar
      Fix merge errors. · 49841a54
      antirez authored
      For some reason I made a merge fiasco between 5.0 and unstable.
      This fixes the error introduced by merging unstable.
      49841a54
  8. 17 Jul, 2018 3 commits
  9. 16 Jul, 2018 5 commits
  10. 14 Jul, 2018 1 commit
  11. 12 Jul, 2018 2 commits
  12. 10 Jul, 2018 3 commits
  13. 09 Jul, 2018 1 commit
  14. 03 Jul, 2018 1 commit
  15. 02 Jul, 2018 1 commit
  16. 27 Jun, 2018 1 commit
  17. 18 Jun, 2018 1 commit
    • antirez's avatar
      Streams: Change XADD MAXLEN handling of values <= 0. · 62f9ac6f
      antirez authored
      Now a MAXLEN of 0 really does what it means: it will create a zero
      entries stream. This is useful in order to make sure that the behavior
      is identical to XTRIM, that must be able to reduce the stream to zero
      elements when MAXLEN is given.
      
      Also now MAXLEN with a count < 0 will return an error.
      62f9ac6f
  18. 17 Jun, 2018 1 commit
  19. 13 Jun, 2018 1 commit
    • antirez's avatar
      Streams: generate a few additional events. · af706962
      antirez authored
      Currently it does not look it's sensible to generate events for streams
      consumer groups modification, being them metadata, however at least for
      key-level events, like the creation or removal of a consumer group, I
      added a few events here and there. Later we can evaluate if it makes
      sense to add more. From the POV instead of WAIT (in Redis transaciton)
      and signaling the key as modified, it looks like that the transaction
      should not fail when a stream is modified, so no calls are made in
      consumer groups related functions to signalModifiedKey().
      af706962