1. 10 Jul, 2018 2 commits
    • antirez's avatar
      Streams: fix new XREADGROUP sync logic. · a8c1bb31
      antirez authored
      a8c1bb31
    • antirez's avatar
      Streams: make blocking for > a truly special case. · 1a02b5f6
      antirez authored
      To simplify the semantics of blocking for a group, this commit changes
      the implementation to better match the description we provide of
      conusmer groups: blocking for > will make the consumer waiting for new
      elements in the group. However blocking for any other ID will always
      serve the local history of the consumer.
      
      However it must be noted that the > ID is actually an alias for the
      special ID ms/seq of UINT64_MAX,UINT64_MAX.
      1a02b5f6
  2. 03 Jul, 2018 1 commit
  3. 02 Jul, 2018 1 commit
  4. 27 Jun, 2018 1 commit
  5. 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
  6. 17 Jun, 2018 1 commit
  7. 12 Jun, 2018 7 commits
  8. 10 Jun, 2018 3 commits
  9. 07 Jun, 2018 3 commits
  10. 06 Jun, 2018 1 commit
  11. 05 Jun, 2018 1 commit
    • antirez's avatar
      Remove XINFO <key> special form. · 9e25f3e1
      antirez authored
      As observed by Michael Grunder this usage while practical is
      inconsistent because for instance it does not work against a key called
      HELP. Removed.
      9e25f3e1
  12. 04 Jun, 2018 2 commits
    • antirez's avatar
      XGROUP SETID implemented + consumer groups core fixes. · 36b392a0
      antirez authored
      Now that we have SETID, the inetrnals of consumer groups should be able
      to handle the case of the same message delivered multiple times just
      as a side effect of calling XREADGROUP. Normally this should never
      happen but if the admin manually "XGROUP SETID mykey mygroup 0",
      messages will get re-delivered to clients waiting for the ">" special
      ID. The consumer groups internals were not able to handle the case of a
      message re-delivered in this circumstances that was already assigned to
      another owner.
      36b392a0
    • antirez's avatar
      XGROUP DESTROY implemented. · 7c6f1be5
      antirez authored
      7c6f1be5
  13. 03 Jun, 2018 1 commit
  14. 25 May, 2018 5 commits
  15. 19 Apr, 2018 2 commits
  16. 18 Apr, 2018 1 commit
  17. 17 Apr, 2018 2 commits
  18. 10 Apr, 2018 3 commits
  19. 21 Mar, 2018 1 commit
  20. 20 Mar, 2018 1 commit
    • antirez's avatar
      CG: propagate XACK by incrementing server.dirty. · 233da29f
      antirez authored
      This should be more than enough, even if in case of partial IDs that are
      not found, we send all the IDs to the slave/AOF, but this is definitely
      a corner case without bad effects if not some wasted space.
      233da29f