Revision e9bc77716308d9f6e2f64c1f8915868875e19f53 authored by Dhruba Borthakur on 19 June 2012, 07:56:07 UTC, committed by Dhruba Borthakur on 19 June 2012, 07:56:07 UTC
Summary: Test Plan: Reviewers: CC: Task ID: # Blame Rev:
1 parent 7e6c9b9
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?
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...