- 12 Jun, 2019 1 commit
-
-
swilly22 authored
-
- 05 May, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 10 Apr, 2019 1 commit
-
-
antirez authored
-
- 24 Mar, 2019 2 commits
-
-
Oran Agra authored
when redis appends the blocked client reply list to the real client, it didn't bother to check if it is in fact the master client. so a slave executing that module command will send replies to the master, causing the master to send the slave error responses, which will mess up the replication offset (slave will advance it's replication offset, and the master does not)
-
Yossi Gottlieb authored
-
- 21 Mar, 2019 3 commits
-
-
Yossi Gottlieb authored
Add a flag to automatically protect filters from being called recursively by their own module.
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
A filter handle is returned and can be used to unregister a filter. In the future it can also be used to further configure or manipulate the filter. Filters are now automatically unregistered when a module unloads.
-
- 19 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 18 Mar, 2019 4 commits
-
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 15 Mar, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 14 Mar, 2019 1 commit
-
-
antirez authored
-
- 13 Mar, 2019 1 commit
-
-
swilly22 authored
-
- 11 Mar, 2019 1 commit
-
-
swilly22 authored
-
- 12 Feb, 2019 1 commit
-
-
Guy Benoish authored
In some cases processMultibulkBuffer uses sdsMakeRoomFor to expand the querybuf, but later in some cases it uses that query buffer as is for an argv element (see "Optimization"), which means that the sds in argv may have a lot of wasted space, and then in case modules keep that argv RedisString inside their data structure, this space waste will remain for long (until restarted from rdb).
-
- 01 Feb, 2019 2 commits
-
-
antirez authored
It does not make much sense to limit what modules can do: the admin should instead limit what module commnads an user may call. So RedisModule_Call() and other module operations should be able to execute everything they want: the limitation should be posed by the API exported by the module itself.
-
antirez authored
-
- 09 Jan, 2019 3 commits
- 20 Dec, 2018 7 commits
- 13 Dec, 2018 1 commit
-
-
Guy Benoish authored
-
- 04 Oct, 2018 1 commit
-
-
Hamid Alaei authored
-
- 01 Oct, 2018 1 commit
-
-
Hamid Alaei authored
-
- 27 Sep, 2018 3 commits
- 26 Sep, 2018 1 commit
-
-
antirez authored
-
- 25 Sep, 2018 3 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Storing the context is useless, because we can't really reuse that later. For instance in the API RM_DictNext() that returns a RedisModuleString for the next key iterated, the user should pass the new context, because we may run the keys of the dictionary in a different context of the one where the dictionary was created. Also the dictionary may be created without a context, but we may still demand automatic memory management for the returned strings while iterating.
-