- 07 Jul, 2019 1 commit
-
-
Itamar Haber authored
Signed-off-by:
Itamar Haber <itamar@redislabs.com>
-
- 13 May, 2019 10 commits
-
-
Yossi Gottlieb authored
-
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.
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
Yossi Gottlieb authored
-
- 10 May, 2019 1 commit
-
-
Yossi Gottlieb authored
-
- 10 Apr, 2019 2 commits
-
-
antirez authored
-
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)
-
- 14 Mar, 2019 10 commits
-
-
antirez authored
-
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).
-
Guy Benoish authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Based on ideas and code in PR #5560 by @MeirShpilraien.
-
antirez authored
-
MeirShpilraien authored
-
- 13 Mar, 2019 2 commits
- 15 Oct, 2018 1 commit
-
-
Hamid Alaei authored
-
- 03 Oct, 2018 13 commits
-
-
Hamid Alaei authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
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.
-
antirez authored
-
antirez authored
By using the "C" suffix for functions getting pointer/len, we can do the same in the future for other modules APIs that need a variant with pointer/len and that are now accepting a RedisModuleString.
-
antirez authored
The burden of having to always create RedisModuleString objects within a module context was too much, especially now that we have threaded operations and modules are doing more interesting things. The context in the string API is currently only used for automatic memory managemnet, so now the API was modified so that the user can opt-out this feature by passing a NULL context.
-
antirez authored
-
antirez authored
-