X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/6e333bbee207941f7a91bab8f90fc9a20d6ef987..6e09ad1c156f10246ccd0f2de5b11a9635e28818:/TODO?ds=inline diff --git a/TODO b/TODO index 41f30741..145ec524 100644 --- a/TODO +++ b/TODO @@ -1,35 +1,45 @@ -Pre 1.1 todo - -* For now only the last argument gets integer encoded, so make sure that: 1) every multi bulk commands implemented will have the last arg that is indeed a value, and not used otherwise. 2) to explicitly call the function to encode the object in MSET and other commands where there are multiple "values". -* Man pages for MSET MSETNX and SRANDMEMBER. -* Hashes (HSET, HGET, HEXISTS, HLEN, ...). -* ZSETs missing stuff: ZINCRBY, ZSCORE. -* An utility able to export an .rdb file into a text-only JSON dump, we can't live anymore without such a tool. Probably an extension to redis-cli. - -After 1.1 todo - -* Expiring algorithm should be adaptive, if there are a lot of keys with an expire set and many of this happen to be already expired it should be, proportionally, more aggressive. - * Add a command to inspect the currently selected DB index - * Consistent hashing implemented in all the client libraries having an user base - * SORT: Don't copy the list into a vector when BY argument is constant. - * SORT ... STORE keyname. Instead to return the SORTed data set it into key. - * Profiling and optimization in order to limit the CPU usage at minimum - * 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. - * Elapsed time in logs for SAVE when saving is going to take more than 2 seconds - * LOCK / TRYLOCK / UNLOCK as described many times in the google group - * Replication automated tests - * some kind of sorted type, example: - ZADD mykey foo 100 - ZADD mykey bar 50 - ZRANGE mykey 0 1 => bar foo - This is able to take elements sorted because a binary tree is used to store - the elements by 'score', with the actual value being the key. On the other - side the type also takes an hash table with key->score mapping, so that when - there is an update we lookup the current score and can traverse the tree. - * BITMAP / BYTEARRAY type? - * LRANGE 4 0 should return the same elements as LRANGE 0 4 but in reverse order (only if we get enough motivated requests about it) - * zmalloc() should avoid to add a private header for archs where there is some other kind of libc-specific way to get the size of a malloced block. - -FUTURE HINTS - -- In memory compression: if in-memory values compression will be implemented, make sure to implement this so that addReply() is able to handle compressed objects, just creating an uncompressed version on the fly and adding this to the output queue instead of the original one. When insetad we need to look at the object string value (SORT BY for example), call a function that will turn the object into an uncompresed one. +Redis TODO +---------- + +WARNING: are you a possible Redis contributor? + Before implementing what is listed in this file + please drop a message in the Redis google group or chat with + antirez or pietern on irc.freenode.org #redis to check if the work + is already in progress and if the feature is still interesting for + us, and *how* exactly this can be implemented to have good changes + of a merge. Otherwise it is probably wasted work! Thank you + + +CLUSTER +======= + +* Implement rehashing and cluster check in redis-trib. +* Reimplement MIGRATE / RESTORE to use just in memory buffers (no disk at + all). This will require touching a lot of the RDB stuff around, but we may + hand with faster persistence for RDB. +* Implement the slave nodes semantics and election. +* Allow redis-trib to create a cluster-wide snapshot (using SYNC). +* Allow redis-trib to restore a cluster-wide snapshot (implement UPLOAD?). + +SCRIPTING +========= + +* SCRIPT FLUSH or alike to start a fresh interpreter? + +OPTIMIZATIONS +============= + +* SORT: Don't copy the list into a vector when BY argument is constant. +* 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. +* Read-only mode for slaves. +* Redis big lists as linked lists of small ziplists? + 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. + +KNOWN BUGS +========== + +* #519: Slave may have expired keys that were never read in the master (so a DEL + is not sent in the replication channel) but are already expired since + a lot of time. Maybe after a given delay that is undoubtably greater than + the replication link latency we should expire this key on the slave on + access?