- 22 Oct, 2018 2 commits
- 19 Oct, 2018 1 commit
-
- 17 Oct, 2018 15 commits
-
-
antirez authored
-
antirez authored
They play better with Lua scripting, otherwise Lua will see status replies as "ok" = "string" which is very odd, and actually as @oranagra reasoned in issue #5456 in the rest of the Redis code base there was no such concern as saving a few bytes when the protocol is emitted.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This avoids issues with having to replicate a command that produced errors.
-
zhaozhao.zz authored
xadd with id * generates random stream id xadd & xtrim with approximate maxlen count may trim stream randomly xinfo may get random radix-tree-keys/nodes xpending may get random idletime xclaim: master and slave may have different idletime in stream
-
antirez authored
-
zhaozhao.zz authored
-
antirez authored
Related to #5426.
-
antirez authored
Related to #5426.
-
antirez authored
Keep vanilla stream commands at toplevel, see #5426.
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
XSTREAM CREATE <key> <id or *> -- Create a new empty stream. XSTREAM SETID <key> <id or $> -- Set the current stream ID.
-
- 15 Oct, 2018 12 commits
-
-
Hamid Alaei authored
-
antirez authored
Related to #5437.
-
antirez authored
Avoid storing the dirty value. See #5437.
-
antirez authored
See #5437 but also I updated a previous usage of the same var name.
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
Because the NACK->consumer is NULL, if idletime < minidle the NACK does not belong to any consumer, then redis will crash in XPENDING.
-
zhaozhao.zz authored
-
antirez authored
-
antirez authored
-
zhaozhao.zz authored
-
antirez authored
Issue #5433.
-
- 10 Oct, 2018 1 commit
-
-
antirez authored
-
- 09 Oct, 2018 9 commits
-
-
antirez authored
Related to #4840. Note that when we re-enter the event loop with aeProcessEvents() we don't process timers, nor before/after sleep callbacks, so we should never end calling freeClientsInAsyncFreeQueue() when re-entering the loop.
-
antirez authored
Related to #4804.
-
antirez authored
The idea is to have an API for the cases like -BUSY state and DEBUG RELOAD where we have to manually deinstall the read handler. See #4804.
-
zhaozhao.zz authored
-
antirez authored
Related to #5201. I removed the !!! Warning part since compared to the other errors, a missing EXEC is in theory a normal happening in the AOF file, at least in theory: may happen in a differnet number of situations, and it's probably better to don't give the user the feeling that something really bad happened.
-
zhaozhao.zz authored
-
antirez authored
See #5141.
-
zhaozhao.zz authored
Slaves and rebooting redis may have different radix tree struct, by different stream* config options. So propagating approximated MAXLEN to AOF/slaves may lead to date inconsistency.
-
zhaozhao.zz authored
-