Add Parquet footer metadata cache for metrics scans#6388
Open
alexanderbianchi wants to merge 1 commit intoquickwit-oss:mainfrom
Open
Add Parquet footer metadata cache for metrics scans#6388alexanderbianchi wants to merge 1 commit intoquickwit-oss:mainfrom
alexanderbianchi wants to merge 1 commit intoquickwit-oss:mainfrom
Conversation
This was referenced May 6, 2026
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.
Summary
ParquetSourcethrough DataFusion'sCachedParquetFileReaderFactoryso Parquet footer and page-index metadata can be reused across scans.Expected impact
This targets the current metrics IO bottleneck where repeated scans spend a large amount of time in Parquet metadata loading/opening before returning rows. Warm runs on the same worker should reduce
metadata_load_time,time_elapsed_opening, andtime_elapsed_scanning_until_datafor repeated access to the same files.This does not cache column data or object-store byte ranges.
bytes_scannedshould remain roughly unchanged until we add a full blob/range cache.Follow-up
For a full file/range cache, DataFusion/object_store OSS gives us range APIs and range coalescing, but not a packaged production byte-cache. The likely Quickwit integration point is either the
QuickwitObjectStoreadapter or the existingquickwit-storageStorageWithCache/StorageCachepath, backed by Foyer or a similar bounded cache.Validation
cargo fmt -p quickwit-df-corecargo test -p quickwit-df-corecargo test -p quickwit-datafusion