Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 86 lines (67 sloc) 3.531 kB
4c22fd3 @antirez TODO udpated
antirez authored
1 Redis TODO
2 ----------
f284d96 @antirez minor TODO change
antirez authored
3
4c22fd3 @antirez TODO udpated
antirez authored
4 WARNING: are you a possible Redis contributor?
5 Before implementing what is listed what is listed in this file
6 please drop a message in the Redis google group or chat with
7 antirez or pietern on irc.freenode.org #redis to check if the work
8 is already in progress and if the feature is still interesting for
9 us, and *how* exactly this can be implemented to have good changes
10 of a merge. Otherwise it is probably wasted work! Thank you
f6b141c @antirez MSET and MSETNX commands implemented
antirez authored
11
bb8716b @antirez TODO updated
antirez authored
12
4e17be0 @antirez TODO update
antirez authored
13 API CHANGES
14 ===========
bb8716b @antirez TODO updated
antirez authored
15
4e17be0 @antirez TODO update
antirez authored
16 * Turn commands into variadic versions when it makes sense, that is, when
17 the variable number of arguments represent values, and there is no conflict
18 with the return value of the command.
e09b518 @antirez useless function removed
antirez authored
19
8905378 @antirez Cluster TODO updated
antirez authored
20 CLUSTER
21 =======
22
23 * Implement rehashing and cluster check in redis-trib.
24 * Reimplement MIGRATE / RESTORE to use just in memory buffers (no disk at
25 all). This will require touching a lot of the RDB stuff around, but we may
26 hand with faster persistence for RDB.
27 * Implement the slave nodes semantics and election.
28 * Allow redis-trib to create a cluster-wide snapshot (using SYNC).
29 * Allow redis-trib to restore a cluster-wide snapshot (implement UPLOAD?).
30
cc9f0ee @antirez TODO list updated
antirez authored
31 APPEND ONLY FILE
32 ================
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
antirez authored
33
cc9f0ee @antirez TODO list updated
antirez authored
34 * in AOF rewirte use HMSET to rewrite small hashes instead of multiple calls
35 to HSET.
3f47797 @antirez TODO list modified. What's planned for 1.4 is now written in the ston…
antirez authored
36
4c22fd3 @antirez TODO udpated
antirez authored
37 OPTIMIZATIONS
38 =============
0188805 @antirez TODO updated
antirez authored
39
bcde637 @antirez TODO updated
antirez authored
40 * Avoid COW due to incrementing the dict iterators counter.
682ac72 @antirez use __attribute__ format in sdscatprintf() when the compiler is GCC. …
antirez authored
41 * SORT: Don't copy the list into a vector when BY argument is constant.
42 * 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.
4c22fd3 @antirez TODO udpated
antirez authored
43 * Read-only mode for slaves.
e9ee513 @antirez TODO modified
antirez authored
44 * Redis big lists as linked lists of small ziplists?
45 Possibly a simple heuristic that join near nodes when some node gets smaller than the low_level, and split it into two if gets bigger than high_level.
cef34df @antirez TODO updated
antirez authored
46
2d9fdb9 @antirez TODO modified
antirez authored
47 REPORTING
48 =========
49
50 * Better INFO output with sections.
51
52 RANDOM
53 ======
54
55 * Clients should be closed as far as the output buffer list is bigger than a given number of elements (configurable in redis.conf)
56 * Should the redis default configuration, and the default redis.conf, just bind 127.0.0.1?
57
cef34df @antirez TODO updated
antirez authored
58 KNOWN BUGS
59 ==========
60
4c22fd3 @antirez TODO udpated
antirez authored
61 * What happens in the following scenario:
62 1) We are reading an AOF file.
63 2) SETEX FOO 5 BAR
64 3) APPEND FOO ZAP
65 What happens if between 1 and 2 for some reason (system under huge load
66 or alike) too many time passes? We should prevent expires while the
67 AOF is loading.
8231b1e @antirez TODO updated
antirez authored
68 * #519: Slave may have expired keys that were never read in the master (so a DEL
69 is not sent in the replication channel) but are already expired since
70 a lot of time. Maybe after a given delay that is undoubltly greater than
71 the replication link latency we should expire this key on the slave on
72 access?
2cffe29 @antirez TODO list modified, trivial change to source code
antirez authored
73
4e17be0 @antirez TODO update
antirez authored
74 DISKSTORE TODO
75 ==============
76
77 * Fix FLUSHALL/FLUSHDB: the queue of pending reads/writes should be handled.
78 * Check that 00/00 and ff/ff exist at startup, otherwise exit with error.
79 * Implement sync flush option, where data is written synchronously on disk when a command is executed.
80 * Implement MULTI/EXEC as transaction abstract API to diskstore.c, with transaction_start, transaction_end, and a journal to recover.
81 * Stop BGSAVE thread on shutdown and any other condition where the child is killed during normal bgsave.
82 * Fix RANDOMKEY to really do something interesting
83 * Fix DBSIZE to really do something interesting
84 * Add a DEBUG command to check if an entry is or not in memory currently
85 * dscache.c near 236, kobj = createStringObject... we could use static obj.
Something went wrong with that request. Please try again.