SMOVE command implemented

[redis.git] / TODO

diff --git a/TODO b/TODO
index 0e1083d97b341a091714907ad4be1b2c37577e47..e236352c53329e5ffc3c3177df1b3dbddb9acf4d 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,12 +1,14 @@
-- GETSET
-- keys expire
-- sunion ssub
-- network layer stresser in test in demo
+BEFORE REDIS 1.0.0-rc1
+
+- SMOVE _key1_ _key2_ _ele_. Pop an element form _key1_ and push (SADD or LPUSH) it nto _key2_.
+- What happens if the saving child gets killed instead to end normally? Handle this.
+- Make sinterstore / unionstore / sdiffstore returning the cardinality of the resulting set.
+- Remove max number of args limit
+- network layer stresser in test in demo, make sure to set/get random streams of data and check that what we read back is byte-by-byte the same.

 - maxclients directive
 - check 'server.dirty' everywere
 - replication automated tests
 - an external tool able to perform the 'difference' between two Redis servers. It's like 'diff', but against Redis servers, and the output is the set of commands needed to turn the first server into the second, suitable to be sent via netcat.
 - maxclients directive
 - check 'server.dirty' everywere
 - replication automated tests
 - an external tool able to perform the 'difference' between two Redis servers. It's like 'diff', but against Redis servers, and the output is the set of commands needed to turn the first server into the second, suitable to be sent via netcat.

-

    $ ./redis-diff 192.168.1.1 192.168.1.2 > diff.txt
    $ cat diff.txt | nc 192.168.1.1 6379
    $ ./redis-diff 192.168.1.1 192.168.1.2
    $ ./redis-diff 192.168.1.1 192.168.1.2 > diff.txt
    $ cat diff.txt | nc 192.168.1.1 6379
    $ ./redis-diff 192.168.1.1 192.168.1.2


@@ -14,4 +16,13 @@
 
 This command should be smart and don't use too much memory, that is, take two connections at the same time against the two servers and perform the comparison key by key. Probably the initial "KEYS *" is unavoidable.
 
 
 This command should be smart and don't use too much memory, that is, take two connections at the same time against the two servers and perform the comparison key by key. Probably the initial "KEYS *" is unavoidable.
 

-- objects sharing, "objectsharing yes", "objectsharingpool 1024"
+- Shutdown must kill other background savings before to start saving. Otherwise the DB can get replaced by the child that rename(2) after the parent for some reason.
+- Add missing commands in documentation
+- Document replication
+- Objects sharing configuration, add the directive "objectsharingpool <size>"
+- Make sure to convert all the fstat() calls to 64bit versions.
+- SINTERCOUNT, SUNIONCOUNT, SDIFFCOUNT
+
+FUTURE HINTS
+
+- 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.