-
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: Invalid comparison operation: Utf8 == Utf8View
error during LEFT ANTI JOIN
#13510
Comments
Related to #13568? I filed that as a separate issue, but it seems like they might have the same root cause. |
@sergiimk are you able to simplify the failing query so that we have the simplest possible reproducer? |
@findepi was slammed this week unfortunately. I will re-test with latest master and try to narrow the issue down this weekend. |
Does the problem go away if you turn off this config setting: https://datafusion.apache.org/user-guide/configs.html datafusion.execution.parquet.schema_force_view_types We are still working through some additional needed support: |
Apologies for the slow turnaround. Sharing findings from today: Compiling with latest After simulating my ANTI JOIN in @alamb setting |
Phew, finally got the minimal repro:
Including the test project with sample data: Still not sure why the same exact scenario didn't break when using Will update the ticket description with the repro. |
Summary:
The error comes from arrow-rs (source https://github.com/apache/arrow-rs/blob/2c84f243b882eff69806cd7294d38bf422fdb24a/arrow-ord/src/cmp.rs#L241 Here is the stack of the error:
I suspect what is needed to fix this issue is to insert a coercsion somewhere in DataFusion so the join key is correctly coerced |
Describe the bug
Between
42.2.0
and43.0.0
there appears to have been a regression that introduced an error:Note that the error happens at the plan execution phase, i.e. plan validation passes successfully.
To Reproduce
Minimal repro is:
Utf8
columns)Utf8View
)LEFT ANTI JOIN
Including a test project with sample data: datafusion-13510.zip
Physical plan:
Expected behavior
No error / error during planning if some operation is invalid
Additional context
No response
The text was updated successfully, but these errors were encountered: