Skip to content

Commit

Permalink
Fix HISTORY.md file for 9.6 release
Browse files Browse the repository at this point in the history
  • Loading branch information
jaykorean committed Aug 20, 2024
1 parent becf868 commit 96315e9
Showing 1 changed file with 3 additions and 8 deletions.
11 changes: 3 additions & 8 deletions HISTORY.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,15 @@
# Rocksdb Change Log
> NOTE: Entries for next release do not go here. Follow instructions in `unreleased_history/README.txt`
## 9.7.0 (08/19/2024)
### New Features
* Introduce a new mutable CF option `paranoid_memory_checks`. It enables additional validation on data integrity during reads/scanning. Currently, skip list based memtable will validate key ordering during look up and scans.

### Public API Changes
* Adds optional installation callback function for remote compaction

## 9.6.0 (08/16/2024)
## 9.6.0 (08/19/2024)
### New Features
* *Best efforts recovery supports recovering to incomplete Version with a clean seqno cut that presents a valid point in time view from the user's perspective, if versioning history doesn't include atomic flush.
* New option `BlockBasedTableOptions::decouple_partitioned_filters` should improve efficiency in serving read queries because filter and index partitions can consistently target the configured `metadata_block_size`. This option is currently opt-in.
* Introduce a new mutable CF option `paranoid_memory_checks`. It enables additional validation on data integrity during reads/scanning. Currently, skip list based memtable will validate key ordering during look up and scans.

### Public API Changes
* Add ticker stats to count file read retries due to checksum mismatch
* Adds optional installation callback function for remote compaction

### Behavior Changes
* There may be less intra-L0 compaction triggered by total L0 size being too small. We now use compensated file size (tombstones are assigned some value size) when calculating L0 size and reduce the threshold for L0 size limit. This is to avoid accumulating too much data/tombstones in L0.
Expand Down

0 comments on commit 96315e9

Please sign in to comment.