-
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 "RowConverter column schema mismatch, expected Utf8 got Dictionary(Int32, Utf8)" after upgrade #8738
Comments
I'd like to take a look into a repro but will not have time for it earlier than this weekend |
Thanks @qrilka -- I am working on a reproducer and I may try and work on it before this weekend as it is blocking our upgrade in IOx. I'll ping you on any PR I may propose |
Reproducer is in #8750 |
Ok, I have figured out what is going on here The original plan is here Details
The
The problem here is that after #8291 the inputs to the UnionExec produce different schemas.
So the |
I am not quite sure what the right fix is yet. Some possibilities:
At the very least, I think the UnionExec should generate a runtime (internal error) when it detects incompatible inputs so it is easier to track down problems like this in the future |
I would have perhaps expected the type coercion machinery to handle this, i.e. option 2 makes sense to me |
I have spent some more time studying the code. There is coercion logic to handle Union inputs to they have the correct types (e.g. adding casts) but this happens at the One potential source of problems is that I started trying locally to make
|
So I have confirmed that when I change the LogicalPlans to match what the ExecutionPlan now does the test passes again. I will try and make a PR to see how it looks |
I thought about this more and I think we should go with backing out this change while we sort out how to handle it better for reasons described on #7647 (comment) |
Describe the bug
@appletreeisyellow is updating DataFusion in InfluxDB and after upgrade some of our queries hit the following error:
To Reproduce
Our current reproducer has customer data that I can't share, but I will create a test case that shows the problem that we can share later.
Expected behavior
The queries should pass
Additional context
I confirmed that when I reverted eb8aff7 / #8291 the problem stopped (see #8740 for the specific change)
The text was updated successfully, but these errors were encountered: