-
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
Inconsistent and incorrect struct
field coercion
#14396
Labels
bug
Something isn't working
Comments
alamb
added a commit
to alamb/datafusion
that referenced
this issue
Feb 1, 2025
alamb
added a commit
that referenced
this issue
Feb 1, 2025
take |
cj-zhukov
pushed a commit
to cj-zhukov/datafusion
that referenced
this issue
Feb 3, 2025
* Fix field name during struct equality coercion * fix bug * Add more tests * Update tests per apache#14396
@Omega359 notes an additional test that would be good: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When coercing structs with different types DataFusion is inconsistent in its behavior. Sometimes it errors and in other times it is inconsistent
To Reproduce
Consider two structs with two fields
They can be coerced to the same field using
UNION
,Likewise with
CASE
they are coerced to the same valueExpected behavior
I believe the field names will be different after
Case
coercion of Structs loses field names #14383However I expect all of the above queries to fail as the field names are incorrect
I expect the following cases to work:
Additional context
@jayzhan211 suggests: https://github.com/apache/datafusion/pull/14384/files#r1937492704
The text was updated successfully, but these errors were encountered: