antirez 36b392a0b2 XGROUP SETID implemented + consumer groups core fixes.
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.
2018-06-04 17:28:03 +02:00
..
2016-04-25 16:49:57 +03:00
2016-06-07 16:46:00 -04:00
2018-03-21 15:34:13 +08:00
2016-04-04 08:50:58 +02:00
2015-10-01 13:02:25 +02:00
2018-05-25 16:49:23 +08:00
2017-12-05 15:38:03 +01:00
2016-07-27 11:34:25 +02:00
2016-07-27 11:34:25 +02:00
2016-06-14 14:45:28 +02:00
2018-03-16 16:57:53 +01:00
2018-02-14 00:12:13 +09:00
2018-05-25 20:16:57 +08:00
2018-06-04 17:26:16 +02:00
2018-06-04 17:26:16 +02:00
2017-01-18 17:12:07 +01:00
2018-05-17 09:52:00 +03:00
2015-04-27 12:07:49 +02:00
2015-04-27 12:07:49 +02:00
2017-02-21 17:07:28 +01:00
2017-12-05 17:42:19 +08:00
2017-01-11 19:24:19 +02:00