-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bloom filter compatibility issue caused by naming #365
Conversation
Signed-off-by: Yang Zhang <[email protected]>
if (key.starts_with(prefix)) { | ||
key.remove_suffix(prefix.size()); | ||
Slice filter_policy_name_slice = Slice(rep_->filter_policy->Name()); | ||
if (key.starts_with("rocksdb.BuiltinBloomFilter") || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add a comment here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Signed-off-by: Yang Zhang <[email protected]> Signed-off-by: v01dstar <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
tikv/tikv#17272
This is a temp fix for 6.29. Will propose a different fix for 8.10.
Since TiKV only uses RocksDB builtin bloom filters, this should be able to fix the issue.
Also planning to revert the PR that introduced this bug in rust-rocksdb, i.e. remove the suffix like ".FullBloom", "BlockBloom" and "Ribbon". After all, "BlockBloom" has been deprecated in RocksDB newer versions anyway.