aboutsummaryrefslogtreecommitdiff
path: root/src/leveldb/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'src/leveldb/TODO')
-rw-r--r--src/leveldb/TODO14
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?