5577130451
CG: Make XINFO Great Again (and more Redis-ish).
...
With XINFO out of the blue I invented a new syntax for commands never
used in Redis in the past... Let's fix it and make it
Great Again!!11one (TM)
2018-03-20 11:52:42 +01:00
2ba9a57c9a
CG: Add JUSTID to XCLAIM propagation to reduce CPU usage.
2018-03-20 11:25:49 +01:00
ad716e29c0
CG: Fix propagate() arg count in streamPropagateXCLAIM().
2018-03-20 11:13:41 +01:00
3cae5f0321
CG: XGROUP CREATE/DELCONUSMER replication.
2018-03-20 11:07:01 +01:00
0b58ad301e
CG: Replication WIP 1: XREADGROUP and XCLAIM propagated as XCLAIM.
2018-03-19 18:02:19 +01:00
6614361615
CG: XINFO STREAM.
2018-03-15 12:54:10 +01:00
d7d8cd0b2f
CG: XINFO GROUPS + output format changes.
...
XINFO is mainly an observability command that will be used more by
humans than computers, and even when used by computers it will be a very
low traffic command. For this reason the format was changed in order to
have field names. They'll consume some bandwidth and CPU cycles, but in
this context this is much better than having to understand what the
numbers in the output array are.
2018-03-15 12:54:10 +01:00
0cf6b1e3ae
CG: XINFO CONSUMERS implemented.
2018-03-15 12:54:10 +01:00
67eeeb0b10
Streams: fix XREAD missing check for NULL object.
2018-03-15 12:54:10 +01:00
8d8755c7b5
CG: throw an error if XREADGROUP is used without GROUP.
2018-03-15 12:54:10 +01:00
d4f81ebdba
CG: XGROUP DELCONSUMER implemented.
2018-03-15 12:54:10 +01:00
9b423ae237
CG: remove stale comment. XREADGROUP is now implemented.
2018-03-15 12:54:10 +01:00
e6d434c167
CG: implement RETRYCOUNT in XCLAIM.
2018-03-15 12:54:10 +01:00
34614a1508
CG: NACK created by XCLAIM FORCE must be set in global PEL.
2018-03-15 12:54:10 +01:00
596264aee9
CG: implement XCLAIM FORCE option.
2018-03-15 12:54:10 +01:00
b26f03bd69
CG: XCLAIM now updates the idle time of the message.
2018-03-15 12:54:10 +01:00
8727b4845b
CG: XCLAIM, use minidle and fix array len.
2018-03-15 12:54:10 +01:00
09e3b3b975
CG: remove unused argument from streamReplyWithRangeFromConsumerPEL().
2018-03-15 12:54:10 +01:00
267f7f2c97
Streams: fix error description for XADD when specified ID is small.
2018-03-15 12:54:10 +01:00
0a6780e560
CG: XCLAIM initial draft.
2018-03-15 12:54:10 +01:00
c9d86c2b16
CG: More specific duplicated group error.
2018-03-15 12:54:10 +01:00
f4e1a4de25
CG: RDB loading first implementation.
2018-03-15 12:54:10 +01:00
e76fb4ab25
CG: XPENDING should not create consumers and obey to count.
2018-03-15 12:54:10 +01:00
f3708af7f9
CG: XPENDING with start/stop/count variant implemented.
2018-03-15 12:54:10 +01:00
1bc31666da
CG: XPENDING without start/stop variant implemented.
2018-03-15 12:54:10 +01:00
b65fe09bb8
CG: Now XREADGROUP + blocking operations work.
2018-03-15 12:54:10 +01:00
5ad29325fe
CG: XACK should return zero when nothing is processed.
2018-03-15 12:54:10 +01:00
388c69fe4e
CG: XACK implementation.
2018-03-15 12:54:10 +01:00
5bbd117c29
CG: XREADGROUP can fetch data from the consumer PEL.
2018-03-15 12:54:10 +01:00
aa808394f6
CG: first draft of streamReplyWithRangeFromConsumerPEL().
2018-03-15 12:54:10 +01:00
bbec4569a5
CG: Fix order of calls in streamReplyWithRange().
...
We need to check if we are going to serve the request via the PEL before
inserting a deferred array len in the client output buffer.
2018-03-15 12:54:10 +01:00
41809fd969
CG: creation of NACK entries in PELs.
2018-03-15 12:54:10 +01:00
1ffb6723f5
CG: fix XREADGROUP ">" special ID parsing due to missing "continue".
2018-03-15 12:54:10 +01:00
6c0af37b6e
CG: streamCompareID() + group last_id updating.
2018-03-15 12:54:10 +01:00
86fe8fde20
CG: consumer lookup + initial streamReplyWithRange() work to supprot CG.
2018-03-15 12:54:10 +01:00
ccdae09046
CG: add & populate group+consumer in the blocking state.
2018-03-15 12:54:10 +01:00
b8e5232161
CG: fix parsing in XREADGROUP and streamLookupCG() NULL check.
2018-03-15 12:54:10 +01:00
2bbb2bf427
CG: XGROUPREAD group option parsing and groups lookup.
2018-03-15 12:54:10 +01:00
1fafe7def1
CG: fix raxFind() retval check in streamCreateCG().
2018-03-15 12:54:10 +01:00
58f0c000a5
CG: data structures design + XGROUP CREATE implementation.
2018-03-15 12:54:10 +01:00
84b281209a
Stream: update the listpack pointer in streamTrimByLength().
2018-03-01 17:26:02 +01:00
2869284e44
Streams: fix a few type mismatches in t_stream.c.
2017-12-04 11:59:15 +01:00
115d076d65
Streams: fix lp-count field for non-same-fields entries.
2017-12-01 10:24:25 +01:00
9bb18e5438
Streams: XRANGE REV option -> XREVRANGE command.
2017-12-01 10:24:25 +01:00
9dc79c039a
Streams: fix reverse iterator discarding of items out of range.
2017-12-01 10:24:25 +01:00
6919280cc5
Streams: fix reverse iteration next node jumping.
2017-12-01 10:24:25 +01:00
ee3490ec48
Streams: state machine for reverse iteration WIP 1.
2017-12-01 10:24:25 +01:00
3c5d773f82
Streams: augment stream entries to allow backward scanning.
2017-12-01 10:24:25 +01:00
020fe26bd6
Streams: fix COUNT parsing, issue #4433 .
2017-12-01 10:24:24 +01:00
5082ec6419
Streams: move ID ms/seq separator from '.' to '-'
...
After checking with the community via Twitter (here:
https://twitter.com/antirez/status/915130876861788161 ) the verdict was to
use ":". However I later realized, after users lamented the fact that
it's hard to copy IDs just with double click, that this was the reason
why I moved to "." in the first instance. Fortunately "-", that was the
other option with most votes, also gets selected with double click on
most terminal applications on Linux and MacOS.
So my reasoning was:
1) We can't retain "." because it's actually confusing to newcomers, it
looks like a floating number, people may be tricked into thinking they
can order IDs numerically as floats.
2) Moving to a double-click-to-select format is much better. People will
work with such IDs for long time when coding / debugging. Why making now
a choice that will impact this for the next years?
The only other viable option was "-", and that's what I did. Thanks.
2017-12-01 10:24:24 +01:00
