Bump org.rocksdb:rocksdbjni from 9.8.4 to 9.10.0

[dependabot]

Bumps org.rocksdb:rocksdbjni from 9.8.4 to 9.10.0.

Release notes

Sourced from org.rocksdb:rocksdbjni's releases.

RocksDB 9.10.0 Release

9.10.0 (2024-12-12)

New Features

• Introduce TransactionOptions::commit_bypass_memtable to enable transaction commit to bypass memtable insertions. This can be beneficial for transactions with many operations, as it reduces commit time that is mostly spent on memtable insertion.

Public API Changes

• Deprecated Remote Compaction APIs (StartV2, WaitForCompleteV2) are completely removed from the codebase

Behavior Changes

• DB::KeyMayExist() now follows its function comment, which means value parameter can be null, and it will be set only if value_found is passed in.

Bug Fixes

• Fix the issue where compaction incorrectly drops a key when there is a snapshot with a sequence number of zero.
• Honor ConfigOptions.ignore_unknown_options in ParseStruct()

Performance Improvements

• Enable reuse of file system allocated buffer for synchronous prefetching.
• In buffered IO mode, try to align writes on power of 2 if checksum handoff is not enabled for the file type being written.

RocksDB release 9.9.3

9.9.3 (2024-12-03)

Performance Improvements

• In buffered IO mode, try to align writes on power of 2 if checksum handoff is not enabled for the file type being written.

9.9.2 (2024-11-22)

Bug Fixes

• Honor ConfigOptions.ignore_unknown_options in ParseStruct()

9.9.1 (2024-11-30)

Behavior Changes

• Updates the hidden hook RocksDbThreadYieldAndCheckAbort() to support MySQL to abort long-running query.

9.9.0 (2024-11-18)

New Features

• Multi-Column-Family-Iterator (CoalescingIterator/AttributeGroupIterator) is no longer marked as experimental
• Adds a new table property "rocksdb.newest.key.time" which records the unix timestamp of the newest key. Uses this table property for FIFO TTL and temperature change compaction.

Public API Changes

• Added a new API Transaction::GetAttributeGroupIterator that can be used to create a multi-column-family attribute group iterator over the specified column families, including the data from both the transaction and the underlying database. This API is currently supported for optimistic and write-committed pessimistic transactions.
• Added a new API Transaction::GetCoalescingIterator that can be used to create a multi-column-family coalescing iterator over the specified column families, including the data from both the transaction and the underlying database. This API is currently supported for optimistic and write-committed pessimistic transactions.

Behavior Changes

• BaseDeltaIterator now honors the read option allow_unprepared_value.

Bug Fixes

• BaseDeltaIterator now calls PrepareValue on the base iterator in case it has been created with the allow_unprepared_value read option set. Earlier, such base iterators could lead to incorrect values being exposed from BaseDeltaIterator.
• Fix a leak of obsolete blob files left open until DB::Close(). This bug was introduced in version 9.4.0.
• Fix missing cases of corruption retry during DB open and read API processing.
• Fix a bug for transaction db with 2pc where an old WAL may be retained longer than needed (#13127).
• Fix leaks of some open SST files (until DB::Close()) that are written but never become live due to various failures. (We now have a check for such leaks with no outstanding issues.)
• Fix a bug for replaying WALs for WriteCommitted transaction DB when its user-defined timestamps setting is toggled on/off between DB sessions.

Performance Improvements

• Fix regression in issue #12038 due to Options::compaction_readahead_size greater than max_sectors_kb (i.e, largest I/O size that the OS issues to a block device defined in linux)

Changelog

Sourced from org.rocksdb:rocksdbjni's changelog.

9.10.0 (12/12/2024)

New Features

• Introduce TransactionOptions::commit_bypass_memtable to enable transaction commit to bypass memtable insertions. This can be beneficial for transactions with many operations, as it reduces commit time that is mostly spent on memtable insertion.

Public API Changes

• Deprecated Remote Compaction APIs (StartV2, WaitForCompleteV2) are completely removed from the codebase

Behavior Changes

• DB::KeyMayExist() now follows its function comment, which means value parameter can be null, and it will be set only if value_found is passed in.

Bug Fixes

• Fix the issue where compaction incorrectly drops a key when there is a snapshot with a sequence number of zero.
• Honor ConfigOptions.ignore_unknown_options in ParseStruct()

Performance Improvements

• Enable reuse of file system allocated buffer for synchronous prefetching.
• In buffered IO mode, try to align writes on power of 2 if checksum handoff is not enabled for the file type being written.

9.9.0 (11/18/2024)

New Features

• Multi-Column-Family-Iterator (CoalescingIterator/AttributeGroupIterator) is no longer marked as experimental
• Adds a new table property "rocksdb.newest.key.time" which records the unix timestamp of the newest key. Uses this table property for FIFO TTL and temperature change compaction.

Public API Changes

• Added a new API Transaction::GetAttributeGroupIterator that can be used to create a multi-column-family attribute group iterator over the specified column families, including the data from both the transaction and the underlying database. This API is currently supported for optimistic and write-committed pessimistic transactions.
• Added a new API Transaction::GetCoalescingIterator that can be used to create a multi-column-family coalescing iterator over the specified column families, including the data from both the transaction and the underlying database. This API is currently supported for optimistic and write-committed pessimistic transactions.

Behavior Changes

• BaseDeltaIterator now honors the read option allow_unprepared_value.

Bug Fixes

• BaseDeltaIterator now calls PrepareValue on the base iterator in case it has been created with the allow_unprepared_value read option set. Earlier, such base iterators could lead to incorrect values being exposed from BaseDeltaIterator.
• Fix a leak of obsolete blob files left open until DB::Close(). This bug was introduced in version 9.4.0.
• Fix missing cases of corruption retry during DB open and read API processing.
• Fix a bug for transaction db with 2pc where an old WAL may be retained longer than needed (#13127).
• Fix leaks of some open SST files (until DB::Close()) that are written but never become live due to various failures. (We now have a check for such leaks with no outstanding issues.)
• Fix a bug for replaying WALs for WriteCommitted transaction DB when its user-defined timestamps setting is toggled on/off between DB sessions.

Performance Improvements

• Fix regression in issue #12038 due to Options::compaction_readahead_size greater than max_sectors_kb (i.e, largest I/O size that the OS issues to a block device defined in linux)

9.8.0 (10/25/2024)

New Features

• All non-block_cache options in BlockBasedTableOptions are now mutable with DB::SetOptions(). See also Bug Fixes below.
• When using iterators with BlobDB, it is now possible to load large values on an on-demand basis, i.e. only if they are actually needed by the application. This can save I/O in use cases where the values associated with certain keys are not needed. For more details, see the new read option allow_unprepared_value and the iterator API PrepareValue.
• Add a new file ingestion option IngestExternalFileOptions::fill_cache to support not adding blocks from ingested files into block cache during file ingestion.
• The option allow_unprepared_value is now also supported for multi-column-family iterators (i.e. CoalescingIterator and AttributeGroupIterator).
• When a file with just one range deletion (standalone range deletion file) is ingested via bulk loading, it will be marked for compaction. During compaction, this type of files can be used to directly filter out some input files that are not protected by any snapshots and completely deleted by the standalone range deletion file.

Behavior Changes

... (truncated)

Commits

• ae8fb3e Explicitly mark destructors with override (#13212)
• 6e8dc74 Add files for 9.10 release
• 7de9c0f Enable commit_bypass_memtable in no_batched_ops_stress tests (#13203)
• 85d8ee7 Improve paranoid_checks API comment (#13206)
• b339d08 Write-side support for FAISS IVF indices (#13197)
• 5aead7a Pass through use_fs_buffer to Read method (#13200)
• d386385 Temporarily disable file system buffer reuse optimization for compaction pref...
• bfe6cc2 Refresh check_buck_targets.sh (#13196)
• 31408c0 Set filesystem constructor parameter for FilePrefetchBuffer inside PrefetchTa...
• be7703b Offline file checksum manifest retriever (#13178)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.