[redis.git] / TODO

BEFORE REDIS 1.0.0-rc1

- What happens if the saving child gets killed instead to end normally? Handle this.
- Fix INCRBY argument that is limited to 32bit int.
- Make sinterstore / unionstore / sdiffstore returning the cardinality of the resulting set.
- Add a new field as INFO output: bgsaveinprogress
- Remove max number of args limit
- GETSET
- 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
- config parameter to change the name of the DB file
- replication automated tests
- replication non stopping master<->slave syncronization
- 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
   $ # No output now the servers are identical

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.

- 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 confert all the fstat() calls to 64bit versions.

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.
Commit	Line	Data
0c66a471	1	BEFORE REDIS 1.0.0-rc1
0c66a471	2
6208b3a7	3	- What happens if the saving child gets killed instead to end normally? Handle this.
5faa6025	4	- Fix INCRBY argument that is limited to 32bit int.
6208b3a7	5	- Make sinterstore / unionstore / sdiffstore returning the cardinality of the resulting set.
cc1db901	6	- Add a new field as INFO output: bgsaveinprogress
05557f6d	7	- Remove max number of args limit
300827b6	8	- GETSET
6208b3a7	9	- 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.
ed9b544e	10	- maxclients directive
ed9b544e	11	- check 'server.dirty' everywere
6208b3a7	12	- config parameter to change the name of the DB file
5a6948fb	13	- replication automated tests
0c66a471	14	- replication non stopping master<->slave syncronization
e3566d4b	15	- 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.
e3566d4b	16	$ ./redis-diff 192.168.1.1 192.168.1.2 > diff.txt
	17	$ cat diff.txt \| nc 192.168.1.1 6379
	18	$ ./redis-diff 192.168.1.1 192.168.1.2
	19	$ # No output now the servers are identical
	20
	21	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.
	22
290deb8b	23	- 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.
	24	- Add missing commands in documentation
	25	- Document replication
	26	- Objects sharing configuration, add the directive "objectsharingpool <size>"
6208b3a7	27	- Make sure to confert all the fstat() calls to 64bit versions.
0c66a471	28
	29	FUTURE HINTS
	30
774e3047	31	- 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.