aleksraiden opened a new pull request, #2864:
URL: https://github.com/apache/kvrocks/pull/2864

   Bump RocksDB to v10.0.1 - a first release at 10.х branch. Full changelog: 
https://github.com/facebook/rocksdb/releases/tag/v10.0.1
   
   **Key updates**:
   
   - Add an unordered map of name/value pairs, ReadOptions::property_bag, to 
pass opaque options through to an external table when creating an Iterator
   - Added a column family option disallow_memtable_writes to safely fail any 
attempts to write to a non-default column family. This can be used for column 
families that are ingest only
   - Added the ability to plug-in a custom table reader implementation
   - Experimental feature: RocksDB now supports FAISS inverted file based 
indices via the secondary indexing framework
   - Add new DB property num_running_compaction_sorted_runs that tracks the 
number of sorted runs being processed by currently running compactions
   - Experimental feature: added support for simple secondary indices that 
index the specified column as-is
   - Updated the query API of the experimental secondary indexing feature by 
removing the earlier SecondaryIndex::NewIterator virtual and adding a 
SecondaryIndexIterator class that can be utilized by applications to find the 
primary keys for a given search target
   - Minimum supported version of ZSTD is now 1.4.0, for code simplification
   - VerifyBackup in verify_with_checksum=true mode will now evaluate checksums 
in parallel
   - Reversed the order of updates to the same key in WriteBatchWithIndex. This 
means if there are multiple updates to the same key, the most recent update is 
ordered first
   - Fix a bug in GetMergeOperands() that can return incorrect status 
(MergeInProgress) and incorrect number of merge operands


-- 
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]

Reply via email to