-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix predicate pushdown bugs: project columns within DatafusionArrowPredicate (#4005) (#4006) #4021
Fix predicate pushdown bugs: project columns within DatafusionArrowPredicate (#4005) (#4006) #4021
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.
I'll plan to merge this in tomorrow unless anyone else would like to comment |
This PR had a conflict after merging #3989 I took the liberty of fixing the merge conflict and pushing the fix. |
Benchmark runs are scheduled for baseline = f4d70ac and contender = 35f786b. 35f786b is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…edicate (apache#4005) (apache#4006) (apache#4021) * Project columns within DatafusionArrowPredicate (apache#4005) (apache#4006) * Add test * Format * Fix merge blunder Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
I found another related bug: #4046 |
…edicate (apache#4005) (apache#4006) (apache#4021) * Project columns within DatafusionArrowPredicate (apache#4005) (apache#4006) * Add test * Format * Fix merge blunder Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
Which issue does this PR close?
Closes #4005
Closes #4006
Rationale for this change
See tickets
What changes are included in this PR?
Project batch in DatafusionArrowPredicate according to the order expected by the PhysicalExpr
Are there any user-facing changes?
No