dependabot[bot] opened a new pull request, #4039: URL: https://github.com/apache/ignite-3/pull/4039
Bumps [org.rocksdb:rocksdbjni](https://github.com/facebook/rocksdb) from 9.2.1 to 9.3.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/rocksdb/releases";>org.rocksdb:rocksdbjni's releases</a>.</em></p> <blockquote> <h2>RocksDB 9.3.1</h2> <h2>9.3.1 (2024-05-25)</h2> <h3>Bug Fixes</h3> <ul> <li>[internal only] Build script improvement</li> </ul> <h2>9.3.0 (2024-05-17)</h2> <h3>New Features</h3> <ul> <li>Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the <code>GetEntity</code> API.</li> <li>Added new <code>Iterator</code> property, "rocksdb.iterator.is-value-pinned", for checking whether the <code>Slice</code> returned by <code>Iterator::value()</code> can be used until the <code>Iterator</code> is destroyed.</li> <li>Optimistic transactions and WriteCommitted pessimistic transactions now support the <code>MultiGetEntity</code> API.</li> <li>Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the <code>PutEntity</code> API. Support for read APIs and other write policies (WritePrepared, WriteUnprepared) will be added later.</li> </ul> <h3>Public API Changes</h3> <ul> <li>Exposed block based metadata cache options via C API</li> <li>Exposed compaction pri via c api.</li> <li>Add a kAdmPolicyAllowAll option to TieredAdmissionPolicy that admits all blocks evicted from the primary block cache into the compressed secondary cache.</li> </ul> <h3>Behavior Changes</h3> <ul> <li>CompactRange() with change_level=true on a CF with FIFO compaction will return Status::NotSupported().</li> <li>External file ingestion with FIFO compaction will always ingest to L0.</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Fixed a bug for databases using <code>DBOptions::allow_2pc == true</code> (all <code>TransactionDB</code>s except <code>OptimisticTransactionDB</code>) that have exactly one column family. Due to a missing WAL sync, attempting to open the DB could have returned a <code>Status::Corruption</code> with a message like "SST file is ahead of WALs".</li> <li>Fix a bug in CreateColumnFamilyWithImport() where if multiple CFs are imported, we were not resetting files' epoch number and L0 files can have overlapping key range but the same epoch number.</li> <li>Fixed race conditions when <code>ColumnFamilyOptions::inplace_update_support == true</code> between user overwrites and reads on the same key.</li> <li>Fix a bug where <code>CompactFiles()</code> can compact files of range conflict with other ongoing compactions' when <code>preclude_last_level_data_seconds > 0</code> is used</li> <li>Fixed a false positive <code>Status::Corruption</code> reported when reopening a DB that used <code>DBOptions::recycle_log_file_num > 0</code> and <code>DBOptions::wal_compression != kNoCompression</code>.</li> <li>While WAL is locked with LockWAL(), some operations like Flush() and IngestExternalFile() are now blocked as they should have been.</li> <li>Fixed a bug causing stale memory access when using the TieredSecondaryCache with an NVM secondary cache, and a file system that supports return an FS allocated buffer for MultiRead (FSSupportedOps::kFSBuffer is set).</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/facebook/rocksdb/blob/v9.3.1/HISTORY.md";>org.rocksdb:rocksdbjni's changelog</a>.</em></p> <blockquote> <h2>9.3.1 (05/25/2024)</h2> <h3>Bug Fixes</h3> <ul> <li>[internal only] Build script improvement</li> </ul> <h2>9.3.0 (05/17/2024)</h2> <h3>New Features</h3> <ul> <li>Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the <code>GetEntity</code> API.</li> <li>Added new <code>Iterator</code> property, "rocksdb.iterator.is-value-pinned", for checking whether the <code>Slice</code> returned by <code>Iterator::value()</code> can be used until the <code>Iterator</code> is destroyed.</li> <li>Optimistic transactions and WriteCommitted pessimistic transactions now support the <code>MultiGetEntity</code> API.</li> <li>Optimistic transactions and pessimistic transactions with the WriteCommitted policy now support the <code>PutEntity</code> API. Support for read APIs and other write policies (WritePrepared, WriteUnprepared) will be added later.</li> </ul> <h3>Public API Changes</h3> <ul> <li>Exposed block based metadata cache options via C API</li> <li>Exposed compaction pri via c api.</li> <li>Add a kAdmPolicyAllowAll option to TieredAdmissionPolicy that admits all blocks evicted from the primary block cache into the compressed secondary cache.</li> </ul> <h3>Behavior Changes</h3> <ul> <li>CompactRange() with change_level=true on a CF with FIFO compaction will return Status::NotSupported().</li> <li>External file ingestion with FIFO compaction will always ingest to L0.</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Fixed a bug for databases using <code>DBOptions::allow_2pc == true</code> (all <code>TransactionDB</code>s except <code>OptimisticTransactionDB</code>) that have exactly one column family. Due to a missing WAL sync, attempting to open the DB could have returned a <code>Status::Corruption</code> with a message like "SST file is ahead of WALs".</li> <li>Fix a bug in CreateColumnFamilyWithImport() where if multiple CFs are imported, we were not resetting files' epoch number and L0 files can have overlapping key range but the same epoch number.</li> <li>Fixed race conditions when <code>ColumnFamilyOptions::inplace_update_support == true</code> between user overwrites and reads on the same key.</li> <li>Fix a bug where <code>CompactFiles()</code> can compact files of range conflict with other ongoing compactions' when <code>preclude_last_level_data_seconds > 0</code> is used</li> <li>Fixed a false positive <code>Status::Corruption</code> reported when reopening a DB that used <code>DBOptions::recycle_log_file_num > 0</code> and <code>DBOptions::wal_compression != kNoCompression</code>.</li> <li>While WAL is locked with LockWAL(), some operations like Flush() and IngestExternalFile() are now blocked as they should have been.</li> <li>Fixed a bug causing stale memory access when using the TieredSecondaryCache with an NVM secondary cache, and a file system that supports return an FS allocated buffer for MultiRead (FSSupportedOps::kFSBuffer is set).</li> </ul> <h2>9.2.0 (05/01/2024)</h2> <h3>New Features</h3> <ul> <li>Added two options <code>deadline</code> and <code>max_size_bytes</code> for CacheDumper to exit early</li> <li>Added a new API <code>GetEntityFromBatchAndDB</code> to <code>WriteBatchWithIndex</code> that can be used for wide-column point lookups with read-your-own-writes consistency. Similarly to <code>GetFromBatchAndDB</code>, the API can combine data from the write batch with data from the underlying database if needed. See the API comments for more details.</li> <li>[Experimental] Introduce two new cross-column-family iterators - CoalescingIterator and AttributeGroupIterator. The CoalescingIterator enables users to iterate over multiple column families and access their values and columns. During this iteration, if the same key exists in more than one column family, the keys in the later column family will overshadow the previous ones. The AttributeGroupIterator allows users to gather wide columns per Column Family and create attribute groups while iterating over keys across all CFs.</li> <li>Added a new API <code>MultiGetEntityFromBatchAndDB</code> to <code>WriteBatchWithIndex</code> that can be used for batched wide-column point lookups with read-your-own-writes consistency. Similarly to <code>MultiGetFromBatchAndDB</code>, the API can combine data from the write batch with data from the underlying database if needed. See the API comments for more details.</li> <li>*Adds a <code>SstFileReader::NewTableIterator</code> API to support programmatically read a SST file as a raw table file.</li> <li>Add an option to <code>WaitForCompactOptions</code> - <code>wait_for_purge</code> to make <code>WaitForCompact()</code> API wait for background purge to complete</li> </ul> <h3>Public API Changes</h3> <ul> <li>DeleteRange() will return NotSupported() if row_cache is configured since they don't work together in some cases.</li> <li>Deprecated <code>CompactionOptions::compression</code> since <code>CompactionOptions</code>'s API for configuring compression was incomplete, unsafe, and likely unnecessary</li> <li>Using <code>OptionChangeMigration()</code> to migrate from non-FIFO to FIFO compaction with <code>Options::compaction_options_fifo.max_table_files_size</code> > 0 can cause the whole DB to be dropped right after migration if the migrated data is larger than <code>max_table_files_size</code></li> </ul> <h3>Behavior Changes</h3> <ul> <li>Enabling <code>BlockBasedTableOptions::block_align</code> is now incompatible (i.e., APIs will return <code>Status::InvalidArgument</code>) with more ways of enabling compression: <code>CompactionOptions::compression</code>, <code>ColumnFamilyOptions::compression_per_level</code>, and <code>ColumnFamilyOptions::bottommost_compression</code>.</li> <li>Changed the default value of <code>CompactionOptions::compression</code> to <code>kDisableCompressionOption</code>, which means the compression type is determined by the <code>ColumnFamilyOptions</code>.</li> <li><code>BlockBasedTableOptions::optimize_filters_for_memory</code> is now set to true by default. When <code>partition_filters=false</code>, this could lead to somewhat increased average RSS memory usage by the block cache, but this "extra" usage is within the allowed memory budget and should make memory usage more consistent (by minimizing internal fragmentation for more kinds of blocks).</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facebook/rocksdb/commit/c5201abc4a983450f9423435a4405829be23d0a8";><code>c5201ab</code></a> update HISTORY.md and version.h for 9.3.1</li> <li><a href="https://github.com/facebook/rocksdb/commit/4eda1b79fa0f5182f63f8ffc07e6685e467842e0";><code>4eda1b7</code></a> add export_file to rockdb TARGETS generator and re-gen</li> <li><a href="https://github.com/facebook/rocksdb/commit/030f7c4a7b270b4ba7fb1b929b92404165291bb1";><code>030f7c4</code></a> include bug fixes in 9.3.0 from after the branch cut until now</li> <li><a href="https://github.com/facebook/rocksdb/commit/6c60c8f3f3242a3cf8735cfc6d2491ab5471f6e0";><code>6c60c8f</code></a> Fix stale memory access with FSBuffer and tiered sec cache (<a href="https://redirect.github.com/facebook/rocksdb/issues/12712";>#12712</a>)</li> <li><a href="https://github.com/facebook/rocksdb/commit/2660754dbc574194f227d64d0e9612ce046a98eb";><code>2660754</code></a> Fix recycled WAL detection when wal_compression is enabled (<a href="https://redirect.github.com/facebook/rocksdb/issues/12643";>#12643</a>)</li> <li><a href="https://github.com/facebook/rocksdb/commit/94a867c8456d6e5f80395adc6f74f71a0aee2edf";><code>94a867c</code></a> Disallow memtable flush and sst ingest while WAL is locked (<a href="https://redirect.github.com/facebook/rocksdb/issues/12652";>#12652</a>)</li> <li><a href="https://github.com/facebook/rocksdb/commit/1b5474c8e1abb1d4471002e2ef3d3e3b8d135885";><code>1b5474c</code></a> Fix unreleased bug fix .md name (<a href="https://redirect.github.com/facebook/rocksdb/issues/12672";>#12672</a>)</li> <li><a href="https://github.com/facebook/rocksdb/commit/b135fa7a8b75b30d084a606450e99511eaf69406";><code>b135fa7</code></a> 9.3.0 release notes</li> <li><a href="https://github.com/facebook/rocksdb/commit/0ed93552f4cd6004e966815e1c18347e01628830";><code>0ed9355</code></a> Implement obsolete file deletion (GC) in follower (<a href="https://redirect.github.com/facebook/rocksdb/issues/12657";>#12657</a>)</li> <li><a href="https://github.com/facebook/rocksdb/commit/ffd7930312dffc6fe7a29e05c4f5870db23869b8";><code>ffd7930</code></a> Add more debug print to <code>DBTestWithParam.ThreadStatusSingleCompaction</code> (<a href="https://redirect.github.com/facebook/rocksdb/issues/12661";>#12661</a>)</li> <li>Additional commits viewable in <a href="https://github.com/facebook/rocksdb/compare/v9.2.1...v9.3.1";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- 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]
