You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for reporting this issue. This feature combination: user-defined timestamp and kDataBlockBinaryAndHash is indeed not compatible. We internally disable this feature combination by making the Comparator:: CanKeysWithDifferentByteContentsBeEqual() return true.
If using timestamp and rocksdb::BlockBasedTableOptions::kDataBlockBinaryAndHash, the returned value in Get() is not the latest value.
Expected behavior
Enabling the index should not affect the returned value.
Actual behavior
The returned value is not the most recent one.
Steps to reproduce the behavior
Tested with rocksdb 8.8.1 and catch2.
The text was updated successfully, but these errors were encountered: