]>
Commit | Line | Data |
---|---|---|
c25e9818 VF |
1 | ss |
2 | - Stats | |
3 | ||
4 | db | |
5 | - Maybe implement DB::BulkDeleteForRange(start_key, end_key) | |
6 | that would blow away files whose ranges are entirely contained | |
7 | within [start_key..end_key]? For Chrome, deletion of obsolete | |
8 | object stores, etc. can be done in the background anyway, so | |
9 | probably not that important. | |
10 | - There have been requests for MultiGet. | |
11 | ||
12 | After a range is completely deleted, what gets rid of the | |
13 | corresponding files if we do no future changes to that range. Make | |
14 | the conditions for triggering compactions fire in more situations? |