-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Fix filter pushdown for extension plans #5425
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
Conversation
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.
Thank you for the contribution @thinkharderdev - the code makes sense to me and I reviewed the test coverage carefully. Thanks again
| .filter(col("a").eq(lit(1i64)).and(col("c").eq(lit(2i64))))? | ||
| .build()?; | ||
|
|
||
| // Push only predicate on `a` below NoopPlan |
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.
👍
jackwener
left a comment
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.
A nice job, thanks @thinkharderdev
Co-authored-by: jakevin <jakevingoo@gmail.com>
|
Benchmark runs are scheduled for baseline = c676d10 and contender = c477fc0. c477fc0 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Closes #5424
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Yes
Are there any user-facing changes?
Predicates will be pushed down through extension plan nodes
No