-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix for issue #6595 has broken existing working queries ("Schema error: No field named ...") #6897
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
Labels
bug
Something isn't working
Comments
I have verified this has been fixed on master (aka what will be released in DataFusion BTW I added new test coverage in #6836 so that we don't break this again by accident. Since it is a regression I would be willing to create a patch release ( Using this query (thanks for the reproducer @maxburke 🙏 ) SELECT
"day" AS "date", count(distinct "direction") AS "num_directions"
FROM 'test_data.parquet'
GROUP BY "day"
ORDER BY "day" ASC;
|
cc @jackwener |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After upgrading to Datafusion 27.0.0 we noticed some of our regression tests were failing. We bisected the commit that introduced the break to 36123ee, which is the fix for #6595.
To Reproduce
The attached zip file contains a parquet file. To reproduce the issue in datafusion-cli, run:
In datafusion 26 and earlier, this will generate a result. In datafusion 27, it generates this error message:
test_data.zip
Expected behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: