]> git.saurik.com Git - redis.git/blame - TODO
TODO updated
[redis.git] / TODO
CommitLineData
f284d963 1Redis TODO and Roadmap
2
2014c437 3VERSION 1.2 TODO (Zsets, Integer encoding, Append only journal)
c35f7d5b 4===============================================================
5
6Most 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:
f6b141c5 7
f284d963 8* Man pages for SRANDMEMBER, missing Z-commands, ...
5b2a1c29 9* Write docs for the "STORE" operaiton of SORT. Link to the article about SORT by written by defunkt.
0188805d 10* Write tests for ZREMRANGEBYSCORE
23cff1a8 11
2014c437 12VERSION 1.4 TODO (Hash type)
c35f7d5b 13============================
23cff1a8 14
15* Hashes (HSET, HGET, HEXISTS, HLEN, ...).
cb7e07cc 16* 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 17
2014c437 18VERSION 1.6 TODO (Virtual memory)
c35f7d5b 19=================================
7d65b33d 20
21* Redis Virtual Memory for datasets bigger than RAM (http://groups.google.com/group/redis-db/msg/752997c7b38553cd)
22
2014c437 23VERSION 1.8 TODO (Fault tollerant sharding)
c35f7d5b 24===========================================
7d65b33d 25
c35f7d5b 26* Redis-cluster, a fast intermediate layer (proxy) that implements consistent hashing and fault tollerant nodes handling.
7d65b33d 27
5b2a1c29 28Interesting readings about this:
29
30 - http://ayende.com/Blog/archive/2009/04/06/designing-rhino-dht-a-fault-tolerant-dynamically-distributed-hash.aspx
31
2014c437 32VERSION 2.0 TODO (Optimizations and latency)
c35f7d5b 33============================================
7d65b33d 34
35* Lower the CPU usage.
36* Lower the RAM usage everywhere possible.
37* Use epool and alike to rewrite ae.c for Linux and other platforms suppporting fater-than-select() mutiplexing APIs.
38* Implement an UDP interface for low-latency GET/SET operations.
39
2014c437 40VERSION 2.2 TODO (Optimizations and latency)
41============================================
42
43* JSON command able to access data serialized in JSON format. For instance if I've a key foobar with a json object I can alter the "name" file using somthing like: "JSON SET foobar name Kevin". We should have GET and INCRBY as well.
44
c35f7d5b 45SHORT/LONG TERM RANDOM TODO ITEMS
46=================================
f6b141c5 47
0188805d 48Most of this can be seen just as proposals, the fact they are in this list
49it's not a guarantee they'll ever get implemented ;)
50
2014c437 51 * FORK command (fork()s executing the commands received by the current
52 client in the new process). Hint: large SORTs can use more cores,
53 copy-on-write will avoid memory problems.
0188805d 54 * DUP command? DUP srckey dstkey, creates an exact clone of srckey value in dstkey.
d214bb48 55 * SORT: Don't copy the list into a vector when BY argument is constant.
391b4a60 56 * 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.
391b4a60 57 * LOCK / TRYLOCK / UNLOCK as described many times in the google group
58 * Replication automated tests
0188805d 59 * Byte Array type (BA prefixed commands): BASETBIT BAGETBIT BASETU8 U16 U32 U64 S8 S16 S32 S64, ability to atomically INCRBY all the base types. BARANGE to get a range of bytes as a bulk value, BASETRANGE to set a range of bytes.
60 * 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. Already done for Mac OS X.
9d65a1bb 61 * Read-only mode.
0188805d 62 * Pattern-matching replication.