Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
12607: deps(maven): bump rocksdbjni from 8.0.0 to 8.1.1.1 r=github-actions[bot] a=dependabot[bot] Bumps [rocksdbjni](https://github.com/facebook/rocksdb) from 8.0.0 to 8.1.1.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/rocksdb/releases">rocksdbjni's releases</a>.</em></p> <blockquote> <h2>RocksDB 8.1.1</h2> <h2>8.1.1 (04/06/2023)</h2> <h3>Bug Fixes</h3> <ul> <li>In the DB::VerifyFileChecksums API, ensure that file system reads of SST files are equal to the readahead_size in ReadOptions, if specified. Previously, each read was 2x the readahead_size.</li> </ul> <h2>8.1.0 (03/18/2023)</h2> <h3>Behavior changes</h3> <ul> <li>Compaction output file cutting logic now considers range tombstone start keys. For example, SST partitioner now may receive ParitionRequest for range tombstone start keys.</li> <li>If the async_io ReadOption is specified for MultiGet or NewIterator on a platform that doesn't support IO uring, the option is ignored and synchronous IO is used.</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Fixed an issue for backward iteration when user defined timestamp is enabled in combination with BlobDB.</li> <li>Fixed a couple of cases where a Merge operand encountered during iteration wasn't reflected in the <code>internal_merge_count</code> PerfContext counter.</li> <li>Fixed a bug in CreateColumnFamilyWithImport()/ExportColumnFamily() which did not support range tombstones (<a href="https://redirect.github.com/facebook/rocksdb/issues/11252">#11252</a>).</li> <li>Fixed a bug where an excluded column family from an atomic flush contains unflushed data that should've been included in this atomic flush (i.e, data of seqno less than the max seqno of this atomic flush), leading to potential data loss in this excluded column family when <code>WriteOptions::disableWAL == true</code> (<a href="https://redirect.github.com/facebook/rocksdb/issues/11148">#11148</a>).</li> </ul> <h3>New Features</h3> <ul> <li>Add statistics rocksdb.secondary.cache.filter.hits, rocksdb.secondary.cache.index.hits, and rocksdb.secondary.cache.filter.hits</li> <li>Added a new PerfContext counter <code>internal_merge_point_lookup_count</code> which tracks the number of Merge operands applied while serving point lookup queries.</li> <li>Add new statistics rocksdb.table.open.prefetch.tail.read.bytes, rocksdb.table.open.prefetch.tail.{miss|hit}</li> <li>Add support for SecondaryCache with HyperClockCache (<code>HyperClockCacheOptions</code> inherits <code>secondary_cache</code> option from <code>ShardedCacheOptions</code>)</li> <li>Add new db properties <code>rocksdb.cf-write-stall-stats</code>, <code>rocksdb.db-write-stall-stats</code>and APIs to examine them in a structured way. In particular, users of <code>GetMapProperty()</code> with property <code>kCFWriteStallStats</code>/<code>kDBWriteStallStats</code> can now use the functions in <code>WriteStallStatsMapKeys</code> to find stats in the map.</li> </ul> <h3>Public API Changes</h3> <ul> <li>Changed various functions and features in <code>Cache</code> that are mostly relevant to custom implementations or wrappers. Especially, asychronous lookup functionality is moved from <code>Lookup()</code> to a new <code>StartAsyncLookup()</code> function.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/facebook/rocksdb/blob/main/HISTORY.md">rocksdbjni's changelog</a>.</em></p> <blockquote> <h1>Rocksdb Change Log</h1> <h2>Unreleased</h2> <h3>New Features</h3> <ul> <li>Introduced a new option <code>block_protection_bytes_per_key</code>, which can be used to enable per key-value integrity protection for in-memory blocks in block cache (<a href="https://redirect.github.com/facebook/rocksdb/issues/11287">#11287</a>).</li> </ul> <h2>8.2.0 (04/24/2023)</h2> <h3>Public API Changes</h3> <ul> <li><code>SstFileWriter::DeleteRange()</code> now returns <code>Status::InvalidArgument</code> if the range's end key comes before its start key according to the user comparator. Previously the behavior was undefined.</li> <li>Add <code>multi_get_for_update</code> to C API.</li> <li>Remove unnecessary constructor for CompressionOptions.</li> </ul> <h3>Behavior changes</h3> <ul> <li>Changed default block cache size from an 8MB to 32MB LRUCache, which increases the default number of cache shards from 16 to 64. This change is intended to minimize cache mutex contention under stress conditions. See <a href="https://github.com/facebook/rocksdb/wiki/Block-Cache">https://github.com/facebook/rocksdb/wiki/Block-Cache</a> for more information.</li> <li>For level compaction with <code>level_compaction_dynamic_level_bytes=true</code>, RocksDB now trivially moves levels down to fill LSM starting from bottommost level during DB open. See more in comments for option <code>level_compaction_dynamic_level_bytes</code> (<a href="https://redirect.github.com/facebook/rocksdb/issues/11321">#11321</a>).</li> <li>User-provided <code>ReadOptions</code> take effect for more reads of non-<code>CacheEntryRole::kDataBlock</code> blocks.</li> <li>For level compaction with <code>level_compaction_dynamic_level_bytes=true</code>, RocksDB now drains unnecessary levels through background compaction automatically (<a href="https://redirect.github.com/facebook/rocksdb/issues/11340">#11340</a>). This together with <a href="https://redirect.github.com/facebook/rocksdb/issues/11321">#11321</a> makes it automatic to migrate other compaction settings to level compaction with <code>level_compaction_dynamic_level_bytes=true</code>. In addition, a live DB that becomes smaller will now have unnecessary levels drained which can help to reduce read and space amp.</li> <li>If <code>CompactRange()</code> is called with <code>CompactRangeOptions::bottommost_level_compaction=kForce*</code> to compact from L0 to L1, RocksDB now will try to do trivial move from L0 to L1 and then do an intra L1 compaction, instead of a L0 to L1 compaction with trivial move disabled (<a href="https://redirect.github.com/facebook/rocksdb/issues/11375">#11375</a>)).</li> </ul> <h3>Bug Fixes</h3> <ul> <li>In the DB::VerifyFileChecksums API, ensure that file system reads of SST files are equal to the readahead_size in ReadOptions, if specified. Previously, each read was 2x the readahead_size.</li> <li>In block cache tracing, fixed some cases of bad hit/miss information (and more) with MultiGet.</li> </ul> <h3>New Features</h3> <ul> <li>Add experimental <code>PerfContext</code> counters <code>iter_{next|prev|seek}_count</code> for db iterator, each counting the times of corresponding API being called.</li> <li>Allow runtime changes to whether <code>WriteBufferManager</code> allows stall or not by calling <code>SetAllowStall()</code></li> <li>Added statistics tickers BYTES_COMPRESSED_FROM, BYTES_COMPRESSED_TO, BYTES_COMPRESSION_BYPASSED, BYTES_COMPRESSION_REJECTED, NUMBER_BLOCK_COMPRESSION_BYPASSED, and NUMBER_BLOCK_COMPRESSION_REJECTED. Disabled/deprecated histograms BYTES_COMPRESSED and BYTES_DECOMPRESSED, and ticker NUMBER_BLOCK_NOT_COMPRESSED. The new tickers offer more inight into compression ratios, rejected vs. disabled compression, etc. (<a href="https://redirect.github.com/facebook/rocksdb/issues/11388">#11388</a>)</li> <li>New statistics <code>rocksdb.file.read.{flush|compaction}.micros</code> that measure read time of block-based SST tables or blob files during flush or compaction.</li> </ul> <h2>8.1.0 (03/18/2023)</h2> <h3>Behavior changes</h3> <ul> <li>Compaction output file cutting logic now considers range tombstone start keys. For example, SST partitioner now may receive ParitionRequest for range tombstone start keys.</li> <li>If the async_io ReadOption is specified for MultiGet or NewIterator on a platform that doesn't support IO uring, the option is ignored and synchronous IO is used.</li> </ul> <h3>Bug Fixes</h3> <ul> <li>Fixed an issue for backward iteration when user defined timestamp is enabled in combination with BlobDB.</li> <li>Fixed a couple of cases where a Merge operand encountered during iteration wasn't reflected in the <code>internal_merge_count</code> PerfContext counter.</li> <li>Fixed a bug in CreateColumnFamilyWithImport()/ExportColumnFamily() which did not support range tombstones (<a href="https://redirect.github.com/facebook/rocksdb/issues/11252">#11252</a>).</li> <li>Fixed a bug where an excluded column family from an atomic flush contains unflushed data that should've been included in this atomic flush (i.e, data of seqno less than the max seqno of this atomic flush), leading to potential data loss in this excluded column family when <code>WriteOptions::disableWAL == true</code> (<a href="https://redirect.github.com/facebook/rocksdb/issues/11148">#11148</a>).</li> </ul> <h3>New Features</h3> <ul> <li>Add statistics rocksdb.secondary.cache.filter.hits, rocksdb.secondary.cache.index.hits, and rocksdb.secondary.cache.filter.hits</li> <li>Added a new PerfContext counter <code>internal_merge_point_lookup_count</code> which tracks the number of Merge operands applied while serving point lookup queries.</li> <li>Add new statistics rocksdb.table.open.prefetch.tail.read.bytes, rocksdb.table.open.prefetch.tail.{miss|hit}</li> <li>Add support for SecondaryCache with HyperClockCache (<code>HyperClockCacheOptions</code> inherits <code>secondary_cache</code> option from <code>ShardedCacheOptions</code>)</li> <li>Add new db properties <code>rocksdb.cf-write-stall-stats</code>, <code>rocksdb.db-write-stall-stats</code>and APIs to examine them in a structured way. In particular, users of <code>GetMapProperty()</code> with property <code>kCFWriteStallStats</code>/<code>kDBWriteStallStats</code> can now use the functions in <code>WriteStallStatsMapKeys</code> to find stats in the map.</li> </ul> <h3>Public API Changes</h3> <ul> <li>Changed various functions and features in <code>Cache</code> that are mostly relevant to custom implementations or wrappers. Especially, asychronous lookup functionality is moved from <code>Lookup()</code> to a new <code>StartAsyncLookup()</code> function.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/facebook/rocksdb/commits">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` 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> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information
