[redis.git] / TODO

VERSION 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, Z-commands, ...
* ZSETs missing stuff: ZINCRBY
* Use strcoll() to compare objects in sorted sets, like it already happens for SORT.
* EXPIRE, EXPIREAT, ZSCORE tests.
* Write docs for the "STORE" operaiton of SORT, and GET "#" option.
* Append only mode: testing and a command to rebuild the log from scratch.
* Profiling and optimizations. For instance the commands lookup is probably starting to eat too CPU being a simple list. To implement binary search or an hash table lookup can be a win probably.
* Redis-cli should be able to select a different DB than 0 using some switch.

VERSION 1.2 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.

LONG TERM TODO

 * 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.

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. (Note, Redis 1.1 beta already has this feature actually, but is for now only used to compress strings representing integers)
Commit	Line	Data
23cff1a8	1	VERSION 1.1 TODO
f6b141c5	2
f6b141c5	3	* 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".
23cff1a8	4	* Man pages for MSET MSETNX and SRANDMEMBER, Z-commands, ...
d7f43c08	5	* ZSETs missing stuff: ZINCRBY
d13f767c	6	* Use strcoll() to compare objects in sorted sets, like it already happens for SORT.
eaa256ad	7	* EXPIRE, EXPIREAT, ZSCORE tests.
eaa256ad	8	* Write docs for the "STORE" operaiton of SORT, and GET "#" option.
cdd140aa	9	* Append only mode: testing and a command to rebuild the log from scratch.
bf75f580	10	* Profiling and optimizations. For instance the commands lookup is probably starting to eat too CPU being a simple list. To implement binary search or an hash table lookup can be a win probably.
12f9d551	11	* Redis-cli should be able to select a different DB than 0 using some switch.
23cff1a8	12
	13	VERSION 1.2 TODO
	14
d13f767c	15	* Basic Redis-cluster (at least all the features of the Ruby client distribute implementation + ability to set every key in M nodes).
23cff1a8	16	* Hashes (HSET, HGET, HEXISTS, HLEN, ...).
cb7e07cc	17	* 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.
f6b141c5	18
23cff1a8	19	LONG TERM TODO
f6b141c5	20
a3b21203	21	* Add a command to inspect the currently selected DB index
391b4a60	22	* Consistent hashing implemented in all the client libraries having an user base
d214bb48	23	* SORT: Don't copy the list into a vector when BY argument is constant.
391b4a60	24	* Profiling and optimization in order to limit the CPU usage at minimum
	25	* 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.
	26	* Elapsed time in logs for SAVE when saving is going to take more than 2 seconds
	27	* LOCK / TRYLOCK / UNLOCK as described many times in the google group
	28	* Replication automated tests
557a74e5	29	* BITMAP / BYTEARRAY type?
ec93bba3	30	* 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.
f2923bec	31
0c66a471	32	FUTURE HINTS
0c66a471	33
23cff1a8	34	- 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)