TODO

   1 Redis TODO
   2 ----------
   3
   4 WARNING: are you a possible Redis contributor?
   5          Before implementing what is listed what is listed in this file
   6          please drop a message in the Redis google group or chat with
   7          antirez or pietern on irc.freenode.org #redis to check if the work
   8          is already in progress and if the feature is still interesting for
   9          us, and *how* exactly this can be implemented to have good changes
  10          of a merge. Otherwise it is probably wasted work! Thank you
  11
  12
  13 API CHANGES
  14 ===========
  15
  16 * Turn commands into variadic versions when it makes sense, that is, when
  17   the variable number of arguments represent values, and there is no conflict
  18   with the return value of the command.
  19
  20 CLUSTER
  21 =======
  22
  23 * Implement rehashing and cluster check in redis-trib.
  24 * Reimplement MIGRATE / RESTORE to use just in memory buffers (no disk at
  25   all). This will require touching a lot of the RDB stuff around, but we may
  26   hand with faster persistence for RDB.
  27 * Implement the slave nodes semantics and election.
  28 * Allow redis-trib to create a cluster-wide snapshot (using SYNC).
  29 * Allow redis-trib to restore a cluster-wide snapshot (implement UPLOAD?).
  30
  31 SCRIPTING
  32 =========
  33
  34 * MULTI/EXEC/...: should we do more than simply ignoring it?
  35 * Prevent Lua from calling itself with redis("eval",...)
  36 * SCRIPT FLUSH or alike to start a fresh interpreter?
  37 * http://redis.io/topics/sponsors
  38
  39 APPEND ONLY FILE
  40 ================
  41
  42 * in AOF rewirte use HMSET to rewrite small hashes instead of multiple calls
  43   to HSET.
  44
  45 OPTIMIZATIONS
  46 =============
  47
  48 * Avoid COW due to incrementing the dict iterators counter.
  49 * SORT: Don't copy the list into a vector when BY argument is constant.
  50 * Write the hash table size of every db in the dump, so that Redis can resize the hash table just one time when loading a big DB.
  51 * Read-only mode for slaves.
  52 * Redis big lists as linked lists of small ziplists?
  53   Possibly a simple heuristic that join near nodes when some node gets smaller than the low_level, and split it into two if gets bigger than high_level.
  54
  55 RANDOM
  56 ======
  57
  58 * Server should abort when getcwd() fails if there is some kind of persistence configured. Check this in the cron loop.
  59 * Clients should be closed as far as the output buffer list is bigger than a given number of elements (configurable in redis.conf)
  60 * Should the redis default configuration, and the default redis.conf, just bind 127.0.0.1?
  61
  62 KNOWN BUGS
  63 ==========
  64
  65 * #519: Slave may have expired keys that were never read in the master (so a DEL
  66   is not sent in the replication channel) but are already expired since
  67   a lot of time. Maybe after a given delay that is undoubltly greater than
  68   the replication link latency we should expire this key on the slave on
  69   access?