bench: multi-conjunct shared-prefix struct row-filter pushdown#23524
Open
SubhamSinghal wants to merge 1 commit into
Open
bench: multi-conjunct shared-prefix struct row-filter pushdown#23524SubhamSinghal wants to merge 1 commit into
SubhamSinghal wants to merge 1 commit into
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
1 participant
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.
Which issue does this PR close?
Rationale for this change
The row-filter planner in
datafusion-datasource-parquetwalks the accessed struct-field paths for every filter, resolves the Parquet leaves, and builds a pruned Arrow schema. When multiple predicates share a common struct prefix, the planner can consolidate that traversal work — this is the case theStructAccessTreerefactor in #23217 is intended to accelerate.The existing bench suite does not cover this shape:
parquet_struct_query— single-field struct predicates only(
WHERE s['id'] = 5).parquet_struct_projection— projection-only, noWHEREclause.So multi-conjunct shared-prefix planning is currently uninstrumented, and the effect of consolidating access-path traversals is invisible against the existing suite.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?
No. Benchmark-only; no library or API surface is touched.