[lake/paimon] Introduce scan-based lake table lookuper - #4124
Open
zuston wants to merge 1 commit into
Open
Conversation
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
this is the sub-task for #3631
The SST-based Paimon lake table lookuper introduced in #3632 caches Paimon SST files on TabletServer local disks. This approach can also benefit from future Fluss-level optimizations, such as a global index.
However, for highly sparse lookup workloads, the cache hit ratio can be very low, resulting in frequent file downloads and additional I/O overhead. Scan-based lookup can reduce this overhead by using predicate pushdown to read only the relevant Parquet row groups instead of entire files. This is particularly beneficial when row groups are small relative to the overall Parquet file size.
Brief change log
Tests
API and Format
Documentation