Add native prepared Parquet batches - #40
Merged
Merged
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.
Summary
prepareScan()sourcesscan()andscanColumn()compatibility; snapshots with delete files use the existing delete-aware row scanner through the bounded row-to-batch adapterEnd-to-end benchmarks
Measured on Node v26.5.1 with
squirreling@0.16.1against two current local Hypaware Iceberg tables containing 339,953 rows. The seven-query suite is derived from Hypaware overview, retrieval, and top-K workloads and filters to the most recent seven days. Before timing each query, the released baseline, same-engine legacy source, and prepared source were exact-compared. Medians are from three alternating runs with explicit garbage collection.The prepared source is 1.31× faster geometrically than the same Squirreling 0.16.1 engine using Icebird's legacy row source, with every query faster. It is 1.35× faster geometrically than the released Icebird 0.8.22 / Squirreling 0.15.3 pair.
The provider/model rollup requested the same 77.49 MiB through both source implementations, attributing its 1.96× improvement to native batching rather than reduced I/O. Peak heap measurements are sampled every 5 ms and are directional.
Validation
npm test— 59 files, 686 tests passednpm run lintnpx tscnpm run build:types— no tracked declaration diffThis depends only on the already-published
squirreling@0.16.1release.