INFO output refactoring. Now "INFO section" will report only the specified section

[redis.git] / TODO

diff --git a/TODO b/TODO
index 3d1059df3cbbca71ea70c250b36c4821fea5b593..0e34b977ae1361da96ed88ff1a065c1a9faa0da4 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,56 +1,58 @@
-Redis TODO and Roadmap
+Redis TODO
+----------

 
 

-VERSION 1.1 TODO (Zsets, Integer encoding, Append only journal)
-===============================================================
+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

 
 

-Most of the features already implemented for this release. The following is a list of the missing things in order to release the first beta tar.gz:
+DISKSTORE TODO
+==============

 
 

-* For now only the last argument gets integer encoded, so make sure that: 1) every multi bulk command 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 SRANDMEMBER, missing Z-commands, ...
-* Use strcoll() to compare objects in sorted sets, like it already happens for SORT.
-* Write docs for the "STORE" operaiton of SORT. Link to the article about SORT by written by defunkt.
-* Append only mode: testing and a command to rebuild the log from scratch.
-* ZRANGEBYSCORE test, ZRANGEBYSCORE LIMIT option.
-* Sorted sets infinity tests.
-* Instead to do the lamest thing of using getDecodedObject only if the encoding
-  of the object != REDIS_ENCODING_RAW, hack getDecodedObject in order to just
-  increment the reference count if the object is already RAW-encoded.
+* 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

 
 

-VERSION 1.2 TODO (Hash type)
-============================
+REPLICATION
+===========

 
 

-* 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.
+* PING between master and slave from time to time, so we can subject the
+master-slave link to timeout, and detect when the connection is gone even
+if the socket is still up.

 
 

-VERSION 1.3 TODO (Virtual memory)
-=================================
+OPTIMIZATIONS
+=============

 
 

-* Redis Virtual Memory for datasets bigger than RAM (http://groups.google.com/group/redis-db/msg/752997c7b38553cd)
+* 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.

 
 

-VERSION 1.4 TODO (Fault tollerant sharding)
-===========================================
+REPORTING
+=========

 
 

-* Redis-cluster, a fast intermediate layer (proxy) that implements consistent hashing and fault tollerant nodes handling.
+* Better INFO output with sections.

 
 

-Interesting readings about this:
+RANDOM
+======

 
 

-    - http://ayende.com/Blog/archive/2009/04/06/designing-rhino-dht-a-fault-tolerant-dynamically-distributed-hash.aspx
+* 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?

 
 

-VERSION 1.5 TODO (Optimizations and latency)
-============================================
+KNOWN BUGS
+==========

 
 

-* Lower the CPU usage.
-* Lower the RAM usage everywhere possible.
-* Use epool and alike to rewrite ae.c for Linux and other platforms suppporting fater-than-select() mutiplexing APIs.
-* Implement an UDP interface for low-latency GET/SET operations.
+* 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.

 
 

-SHORT/LONG TERM RANDOM TODO ITEMS
-=================================
-
- * 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.
- * LOCK / TRYLOCK / UNLOCK as described many times in the google group
- * Replication automated tests
- * BYTEDARRAY 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.
- * Read-only mode.