Push down Parquet scans with delete-aware ranges - #43
Merged
Conversation
Use hyparquet scan candidates for prepared and materialized reads, preserve Iceberg position/equality deletes, and adapt initial footer fetches for small Parquet files.
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
Closes #41.
Performance
Real HypAware cache
hypaware query overview --json --days 7 --include-local-onlyagainst a local cache containing 1,374 Parquet files. Implementations alternated each iteration, with two warmups per implementation and 11 measured runs:A separate seven-run confirmation measured +1.12%. The non-delete many-file path is therefore effectively at parity, with a repeatable approximately 1% cost.
Selective reads and deletes
The count-with-delete read volume fell from 2.491 MiB to 0.125 MiB. The selective payload query fell from 2.491 MiB to 0.388 MiB.
Footer range traffic
A read-only snapshot of 974 production Parquet files was evaluated using their actual file and footer lengths:
This is a 24.8% reduction in initial metadata traffic without another range request. The largest observed footer on a file below 8 MiB was 81.2 KiB. On the 160 raw AI gateway log files alone, the reduction was 22.5%.
Validation
npm test— 59 files, 702 tests passednpm run lintnpx tsc