smengcl opened a new pull request, #9813:
URL: https://github.com/apache/ozone/pull/9813

   Generated-by: GPT-5.3-Codex
   
   ## What changes were proposed in this pull request?
   
   Bump RocksDB version from 7.7.3 to ~~10.4.2~~ 10.10.1. While maintaining 
compatibility and not breaking anything.
   
   1. Since RocksDB 9, BlockBasedTableOptions.format_version=6 is the default. 
Files written in format_version 6 cannot be read by RocksDB < 8.6.0. This PR 
explicitly sets the default to version 5 to be compatible with 7.7.3 in the 
case where Ozone gets downgraded before it gets finalized after an upgrade. 
ref: https://github.com/facebook/rocksdb/releases/tag/v9.0.0
   2. DO NOT MERGE until v10.9.0 or higher RocksDB JNI is available. Potential 
forward compatibility bug < v10.9.0: 
https://github.com/facebook/rocksdb/releases/tag/v10.9.1
   
   > Fix a bug where compaction with range deletion can persist kTypeMaxValid 
in MANIFEST as file metadata. kTypeMaxValid is not supposed to be persisted and 
can change as new value types are introduced. This can cause a forward 
compatibility issue where older versions of RocksDB don't recognize 
kTypeMaxValid from newer versions. A new placeholder value type 
kTypeTruncatedRangeDeletionSentinel is also introduced to replace kTypeMaxValid 
when reading existing SST files' metadata from MANIFEST. This allows us to 
strengthen some checks to avoid using kTypeMaxValid in the future.
   
   3. Currently in this PR I am using a rocksdbjni 10.10.1 fatjar I built 
myself and pushed to maven central snapshot. We need to properly publish it 
(for example, under Apache Ozone account) before we can merge this.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-14225
   
   ## How was this patch tested?
   
   - Most RocksDB related tests are fixed.
   - Pending full CI.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to