update HISTORY.md for 9.4.fb

diff --git a/HISTORY.md b/HISTORY.md
index a1700f993a4de43c3a53ff85cdc783db5e4e0fe6..234780a740872c5da378d313864ffa66f8d3fa50 100644 (file)
--- a/HISTORY.md
+++ b/HISTORY.md
@@ -1,6 +1,31 @@
 # Rocksdb Change Log
 > NOTE: Entries for next release do not go here. Follow instructions in `unreleased_history/README.txt`
 
+## 9.4.0 (06/23/2024)
+### New Features
+* Added a `CompactForTieringCollectorFactory` to auto trigger compaction for tiering use case.
+* Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the `GetEntityForUpdate` API.
+* Added a new "count" command to the ldb repl shell. By default, it prints a count of keys in the database from start to end. The options --from=<key> and/or --to=<key> can be specified to limit the range.
+* Add `rocksdb_writebatch_update_timestamps`, `rocksdb_writebatch_wi_update_timestamps` in C API.
+* Add `rocksdb_iter_refresh` in C API.
+* Add `rocksdb_writebatch_create_with_params`, `rocksdb_writebatch_wi_create_with_params` to create WB and WBWI with all options in C API
+
+### Public API Changes
+* Deprecated names `LogFile` and `VectorLogPtr` in favor of new names `WalFile` and `VectorWalPtr`.
+* Introduce a new universal compaction option CompactionOptionsUniversal::max_read_amp which allows user to define the limit on the number of sorted runs separately from the trigger for compaction (`level0_file_num_compaction_trigger`) #12477.
+
+### Behavior Changes
+* Inactive WALs are immediately closed upon being fully sync-ed rather than in a background thread. This is to ensure LinkFile() is not called on files still open for write, which might not be supported by some FileSystem implementations. This should not be a performance issue, but an opt-out is available with with new DB option `background_close_inactive_wals`.
+
+### Bug Fixes
+* Fix a rare case in which a hard-linked WAL in a Checkpoint is not fully synced (so might lose data on power loss).
+* Fixed the output of the `ldb dump_wal` command for `PutEntity` records so it prints the key and correctly resets the hexadecimal formatting flag after printing the wide-column entity.
+* Fixed an issue where `PutEntity` records were handled incorrectly while rebuilding transactions during recovery.
+* Various read operations could ignore various ReadOptions that might be relevant. Fixed many such cases, which can result in behavior change but a better reflection of specified options.
+
+### Performance Improvements
+* Improved write throughput to memtable when there's a large number of concurrent writers and allow_concurrent_memtable_write=true(#12545)
+
 ## 9.3.0 (05/17/2024)
 ### New Features
 * Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the `GetEntity` API.

diff --git a/unreleased_history/behavior_changes/aggressive_close_inactive_wals.md b/unreleased_history/behavior_changes/aggressive_close_inactive_wals.md
deleted file mode 100644 (file)
index c75f598..0000000
--- a/unreleased_history/behavior_changes/aggressive_close_inactive_wals.md
+++ /dev/null
@@ -1 +0,0 @@
-* Inactive WALs are immediately closed upon being fully sync-ed rather than in a background thread. This is to ensure LinkFile() is not called on files still open for write, which might not be supported by some FileSystem implementations. This should not be a performance issue, but an opt-out is available with with new DB option `background_close_inactive_wals`.

diff --git a/unreleased_history/bug_fixes/checkpoint_unsynced_wal_fix.md b/unreleased_history/bug_fixes/checkpoint_unsynced_wal_fix.md
deleted file mode 100644 (file)
index 35b0622..0000000
--- a/unreleased_history/bug_fixes/checkpoint_unsynced_wal_fix.md
+++ /dev/null
@@ -1 +0,0 @@
-* Fix a rare case in which a hard-linked WAL in a Checkpoint is not fully synced (so might lose data on power loss).

diff --git a/unreleased_history/bug_fixes/ldb_dump_wal_put_entity.md b/unreleased_history/bug_fixes/ldb_dump_wal_put_entity.md
deleted file mode 100644 (file)
index 5a77642..0000000
--- a/unreleased_history/bug_fixes/ldb_dump_wal_put_entity.md
+++ /dev/null
@@ -1 +0,0 @@
-Fixed the output of the `ldb dump_wal` command for `PutEntity` records so it prints the key and correctly resets the hexadecimal formatting flag after printing the wide-column entity.

diff --git a/unreleased_history/bug_fixes/put_entity_rebuild_txn.md b/unreleased_history/bug_fixes/put_entity_rebuild_txn.md
deleted file mode 100644 (file)
index 8793c0f..0000000
--- a/unreleased_history/bug_fixes/put_entity_rebuild_txn.md
+++ /dev/null
@@ -1 +0,0 @@
-Fixed an issue where `PutEntity` records were handled incorrectly while rebuilding transactions during recovery.

diff --git a/unreleased_history/bug_fixes/read_options.md b/unreleased_history/bug_fixes/read_options.md
deleted file mode 100644 (file)
index 931748e..0000000
--- a/unreleased_history/bug_fixes/read_options.md
+++ /dev/null
@@ -1 +0,0 @@
-* Various read operations could ignore various ReadOptions that might be relevant. Fixed many such cases, which can result in behavior change but a better reflection of specified options.

diff --git a/unreleased_history/new_features/auto_trigger_compaction_for_tiering.md b/unreleased_history/new_features/auto_trigger_compaction_for_tiering.md
deleted file mode 100644 (file)
index 973b40b..0000000
--- a/unreleased_history/new_features/auto_trigger_compaction_for_tiering.md
+++ /dev/null
@@ -1 +0,0 @@
-Added a `CompactForTieringCollectorFactory` to auto trigger compaction for tiering use case.
\ No newline at end of file

diff --git a/unreleased_history/new_features/get_entity_for_update.md b/unreleased_history/new_features/get_entity_for_update.md
deleted file mode 100644 (file)
index 2a9c2af..0000000
--- a/unreleased_history/new_features/get_entity_for_update.md
+++ /dev/null
@@ -1 +0,0 @@
-Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the `GetEntityForUpdate` API.

diff --git a/unreleased_history/new_features/ldb_count_command.md b/unreleased_history/new_features/ldb_count_command.md
deleted file mode 100644 (file)
index d631222..0000000
--- a/unreleased_history/new_features/ldb_count_command.md
+++ /dev/null
@@ -1 +0,0 @@
-Added a new "count" command to the ldb repl shell. By default, it prints a count of keys in the database from start to end. The options --from=<key> and/or --to=<key> can be specified to limit the range.

diff --git a/unreleased_history/new_features/write_batch_c_api b/unreleased_history/new_features/write_batch_c_api
deleted file mode 100644 (file)
index 150af09..0000000
--- a/unreleased_history/new_features/write_batch_c_api
+++ /dev/null
@@ -1,3 +0,0 @@
-* Add `rocksdb_writebatch_update_timestamps`, `rocksdb_writebatch_wi_update_timestamps` in C API.
-* Add `rocksdb_iter_refresh` in C API.
-* Add `rocksdb_writebatch_create_with_params`, `rocksdb_writebatch_wi_create_with_params` to create WB and WBWI with all options in C API

diff --git a/unreleased_history/performance_improvements/parallel_notify-one_i_LaunchParallelMemTableWriters.md b/unreleased_history/performance_improvements/parallel_notify-one_i_LaunchParallelMemTableWriters.md
deleted file mode 100644 (file)
index 8fbfca1..0000000
--- a/unreleased_history/performance_improvements/parallel_notify-one_i_LaunchParallelMemTableWriters.md
+++ /dev/null
@@ -1 +0,0 @@
-Improved write throughput to memtable when there's a large number of concurrent writers and allow_concurrent_memtable_write=true(#12545)
\ No newline at end of file

diff --git a/unreleased_history/public_api_changes/rename_to_wal_file.md b/unreleased_history/public_api_changes/rename_to_wal_file.md
deleted file mode 100644 (file)
index 58df40c..0000000
--- a/unreleased_history/public_api_changes/rename_to_wal_file.md
+++ /dev/null
@@ -1 +0,0 @@
-* Deprecated names `LogFile` and `VectorLogPtr` in favor of new names `WalFile` and `VectorWalPtr`.

diff --git a/unreleased_history/public_api_changes/universal_max_read_amp.md b/unreleased_history/public_api_changes/universal_max_read_amp.md
deleted file mode 100644 (file)
index 0c10a37..0000000
--- a/unreleased_history/public_api_changes/universal_max_read_amp.md
+++ /dev/null
@@ -1 +0,0 @@
-* Introduce a new universal compaction option CompactionOptionsUniversal::max_read_amp which allows user to define the limit on the number of sorted runs separately from the trigger for compaction (`level0_file_num_compaction_trigger`) #12477. 
\ No newline at end of file