-
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
Regression in 22.0.0 with filter push-down #5949
Comments
The issue seems to have been introduced in #5831. @jackwener do you know why this PR would have introduced this change in behavior? |
It seems that this plan is unreasonable.
In my opinion, origin how do you think about it, cc @alamb @mingmwang @liukun4515 |
hi, @jackwener before rebase with main ,it's work fine,after rebase,got error.
before PushDownProjection::
after PushDownProjection::
To Reproduce
|
It indeed is covered by
After I investigate it, I find the cause of this problem. This plan is wrong, but because of we don't have analyzer, so the wrong plan was cover by After |
So, I think it isn't a regression. But, If we want to support it, I think we can add a analyzer rule to add missing column. I'm not sure if we need to do this. |
I agree, the program as shown in the description should fail |
Thanks for looking into this. I updated the tests to perform the filter before the projection. |
Describe the bug
The following code is from a unit test in arrow-datafusion-python. It works correctly with DataFusion 21.1.0.
When I upgrade to DF 22.0.0, it fails with:
To Reproduce
See apache/datafusion-python#320
Expected behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: