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 2.6
  14 ===
  15
  16 * Everything under the "SCRIPTING" section.
  17
  18 CLUSTER
  19 =======
  20
  21 * Implement rehashing and cluster check in redis-trib.
  22 * Reimplement MIGRATE / RESTORE to use just in memory buffers (no disk at
  23   all). This will require touching a lot of the RDB stuff around, but we may
  24   hand with faster persistence for RDB.
  25 * Implement the slave nodes semantics and election.
  26 * Allow redis-trib to create a cluster-wide snapshot (using SYNC).
  27 * Allow redis-trib to restore a cluster-wide snapshot (implement UPLOAD?).
  28
  29 SCRIPTING
  30 =========
  31
  32 * MULTI/EXEC/...: should we do more than simply ignoring it?
  33 * Prevent Lua from calling itself with redis("eval",...)
  34 * SCRIPT FLUSH or alike to start a fresh interpreter?
  35 * Check better the replication handling.
  36 * Prevent execution of writes if random commands are used.
  37
  38 OPTIMIZATIONS
  39 =============
  40
  41 * SORT: Don't copy the list into a vector when BY argument is constant.
  42 * 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.
  43 * Read-only mode for slaves.
  44 * Redis big lists as linked lists of small ziplists?
  45   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.
  46
  47 KNOWN BUGS
  48 ==========
  49
  50 * #519: Slave may have expired keys that were never read in the master (so a DEL
  51   is not sent in the replication channel) but are already expired since
  52   a lot of time. Maybe after a given delay that is undoubtably greater than
  53   the replication link latency we should expire this key on the slave on
  54   access?