xref: /aosp_15_r20/external/leveldb/TODO (revision 9507f98c5f32dee4b5f9e4a38cd499f3ff5c4490)
1*9507f98cSAndroid Build Coastguard Workerss
2*9507f98cSAndroid Build Coastguard Worker- Stats
3*9507f98cSAndroid Build Coastguard Worker
4*9507f98cSAndroid Build Coastguard Workerdb
5*9507f98cSAndroid Build Coastguard Worker- Maybe implement DB::BulkDeleteForRange(start_key, end_key)
6*9507f98cSAndroid Build Coastguard Worker  that would blow away files whose ranges are entirely contained
7*9507f98cSAndroid Build Coastguard Worker  within [start_key..end_key]?  For Chrome, deletion of obsolete
8*9507f98cSAndroid Build Coastguard Worker  object stores, etc. can be done in the background anyway, so
9*9507f98cSAndroid Build Coastguard Worker  probably not that important.
10*9507f98cSAndroid Build Coastguard Worker- There have been requests for MultiGet.
11*9507f98cSAndroid Build Coastguard Worker
12*9507f98cSAndroid Build Coastguard WorkerAfter a range is completely deleted, what gets rid of the
13*9507f98cSAndroid Build Coastguard Workercorresponding files if we do no future changes to that range.  Make
14*9507f98cSAndroid Build Coastguard Workerthe conditions for triggering compactions fire in more situations?
15