feat(file_index): add Java-compatible Bloom filter index - #744
Open
QuakeWang wants to merge 1 commit into
Open
Conversation
Signed-off-by: QuakeWang <wangfuzheng0814@foxmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
The file-index foundation only provided generic predicate plumbing and had no concrete Bloom implementation. Rust therefore could not read or produce Java Paimon BloomFilter64 payloads or use them for conservative file pruning.
Linked issue: N/A
Brief change log
EqandInevaluation and strict config/payload validation.Tests
cargo fmt --all -- --checkcargo clippy --locked --all-targets --workspace --features fulltext,vortex -- -D warningscargo test --locked -p paimon --all-targets --features fulltext,vortexAPI and Format
No public API change. The serialized Bloom payload is compatible with Java Paimon. Scan and data-writer integration are not included.
Documentation
No documentation update is required because the feature is not externally exposed yet.