Summary: These files are not relevant anymore. Test Plan: Reviewers: CC: Task ID: # Blame Rev:main
Dhruba Borthakur
12 years ago
parent
772f75b3fb
commit
16e96b1242
@ -1,8 +0,0 @@ |
||||
# Names should be added to this file like so: |
||||
# Name or Organization <email address> |
||||
|
||||
Google Inc. |
||||
|
||||
# Initial version authors: |
||||
Jeffrey Dean <jeff@google.com> |
||||
Sanjay Ghemawat <sanjay@google.com> |
||||
@ -1,17 +0,0 @@ |
||||
Release 1.2 2011-05-16 |
||||
---------------------- |
||||
|
||||
Fixes for larger databases (tested up to one billion 100-byte entries, |
||||
i.e., ~100GB). |
||||
|
||||
(1) Place hard limit on number of level-0 files. This fixes errors |
||||
of the form "too many open files". |
||||
|
||||
(2) Fixed memtable management. Before the fix, a heavy write burst |
||||
could cause unbounded memory usage. |
||||
|
||||
A fix for a logging bug where the reader would incorrectly complain |
||||
about corruption. |
||||
|
||||
Allow public access to WriteBatch contents so that users can easily |
||||
wrap a DB. |
||||
@ -1,13 +0,0 @@ |
||||
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? |
||||
Loading…
Reference in new issue