diff options
| author | Vinnie Falco <vinnie.falco@gmail.com> | 2013-05-03 19:06:59 -0700 |
|---|---|---|
| committer | Vinnie Falco <vinnie.falco@gmail.com> | 2013-05-03 19:06:59 -0700 |
| commit | 80744b3beeab9b25be46e122e6648ba9a0c46e5f (patch) | |
| tree | c0712b4839fd1518db5bdf432868d7f9c95256fc /src/leveldb/TODO | |
| parent | 64753f0438f66c51ba7ae2173120ae97f22d186e (diff) | |
| parent | c25e98186d0f716451ef000e55646d25e014f573 (diff) | |
Merge commit 'c25e98186d0f716451ef000e55646d25e014f573' as 'src/leveldb'
Diffstat (limited to 'src/leveldb/TODO')
| -rw-r--r-- | src/leveldb/TODO | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/src/leveldb/TODO b/src/leveldb/TODO new file mode 100644 index 0000000000..e603c07137 --- /dev/null +++ b/src/leveldb/TODO @@ -0,0 +1,14 @@ +ss +- Stats + +db +- Maybe implement DB::BulkDeleteForRange(start_key, end_key) + that would blow away files whose ranges are entirely contained + within [start_key..end_key]? For Chrome, deletion of obsolete + object stores, etc. can be done in the background anyway, so + probably not that important. +- There have been requests for MultiGet. + +After a range is completely deleted, what gets rid of the +corresponding files if we do no future changes to that range. Make +the conditions for triggering compactions fire in more situations? |