-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor: Add tests for using FilterExec when parquet was pushed down #12362
Conversation
02)--TableScan: alltypes_plain projection=[id], partial_filters=[alltypes_plain.id > Int32(3)] | ||
physical_plan | ||
01)CoalesceBatchesExec: target_batch_size=8192 | ||
02)--FilterExec: id@0 > 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The goal of #4028 is to remove this FilterExec
782509b
to
62dfe90
Compare
62dfe90
to
bbe30e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test case makes sense to me 👍
statement ok | ||
set datafusion.execution.parquet.pushdown_filters = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth setting this to false before creation of t
explicitly, or reckon it's unnecessary and fine to rely on defaults?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a good idea to make it explicit -- I will do so and add a comment about that (update in 2373f37)
Thanks again @Jefffrey for your review |
Which issue does this PR close?
Part of #4028
Rationale for this change
While reviewing #12135 from @itsjunetime I wanted to make sure everything was hooked up end to end and that the appropriate plan changes were done.
I figured I would write such tests as part of my review, though for some reason the PR doesn't actually improve these plans (I will comment on that separately).
What changes are included in this PR?
This adds "end to end" tests that show what should happen when parquet filter pushdown is enabled (specifically the FilterExec should be gone)
Are these changes tested?
yes, only tests
Are there any user-facing changes?
No, only tests