Revision 5f91868ceea5767402390b63c36a3e1958e4fa31 authored by Dhruba Borthakur on 06 November 2012, 00:51:55 UTC, committed by Dhruba Borthakur on 06 November 2012, 00:51:55 UTC
Conflicts: db/version_set.cc util/options.cc
TODO
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.
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?
Computing file changes ...
