Undo rename of function names where something went wrong

[redis.git] / TODO

diff --git a/TODO b/TODO
index c3175783db99c866d98cbc892983dbb2b04bf3de..edcd2b3283a8498206f2c70cb21e1d6918c58b9b 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,31 +1,57 @@
-VERSION 1.1 TODO
+Redis 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, Z-commands, ...
-* Use strcoll() to compare objects in sorted sets, like it already happens for SORT.
-* Tests for: ZINCRBY, SRANDMEMBER, SORT with #.
-* Write docs for the "STORE" operaiton of SORT, and GET "#" option.
-* Append only mode: testing and a command to rebuild the log from scratch.
+WARNING: are you a possible Redis contributor?
+         Before implementing what is listed 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

 
 

-VERSION 1.2 TODO
+DISKSTORE TODO
+==============

 
 

-* Basic Redis-cluster (at least all the features of the Ruby client distribute implementation + ability to set every key in M nodes).
-* Hashes (HSET, HGET, HEXISTS, HLEN, ...).
-* 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.
+* Check that 00/00 and ff/ff exist at startup, otherwise exit with error.
+* Implement sync flush option, where data is written synchronously on disk when a command is executed.
+* Implement MULTI/EXEC as transaction abstract API to diskstore.c, with transaction_start, transaction_end, and a journal to recover.
+* Stop BGSAVE thread on shutdown and any other condition where the child is killed during normal bgsave.
+* Fix RANDOMKEY to really do something interesting
+* Fix DBSIZE to really do something interesting
+* Add a DEBUG command to check if an entry is or not in memory currently

 
 

-LONG TERM TODO
+APPEND ONLY FILE
+================

 
 

- * 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.
- * 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
- * BITMAP / BYTEARRAY type?
- * 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.
+* in AOF rewirte use HMSET to rewrite small hashes instead of multiple calls
+  to HSET.

 
 

-FUTURE HINTS
+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.
+
+REPORTING
+=========
+
+* Better INFO output with sections.
+
+RANDOM
+======
+
+* Clients should be closed as far as the output buffer list is bigger than a given number of elements (configurable in redis.conf)
+* Should the redis default configuration, and the default redis.conf, just bind 127.0.0.1?
+
+KNOWN BUGS
+==========
+
+* What happens in the following scenario:
+    1) We are reading an AOF file.
+    2) SETEX FOO 5 BAR
+    3) APPEND FOO ZAP
+    What happens if between 1 and 2 for some reason (system under huge load
+    or alike) too many time passes? We should prevent expires while the
+    AOF is loading.

 
 

-- 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. (Note, Redis 1.1 beta already has this feature actually, but is for now only used to compress strings representing integers)