-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
sql: panic: invalid datum type given: string[], expected int[] #42320
Comments
Here's another that feels the same:
|
There are others too. I think there's an error being thrown on distsql nodes that don't expect errors and instead panic? That's a pure guess based on past experience. |
That second one is confusing looking - is it on an old version? The optimizer doesn't seem to be getting invoked. |
These all happened last night on I assume what was master. |
https://teamcity.cockroachdb.com/repository/download/Cockroach_Nightlies_WorkloadNightly/1580926:id/sqlsmith/setup%3Drand-tables/setting%3Dno-mutations/1.logs/cockroach.log is another with a JSON encoding internal error (#42102 (comment)). |
That one is expected (there's an issue for it being a terrible error message) - we can't group by json columns. |
But that (the JSON one) was not just a bad error message, it was an internal error, which indicates some other problem, right? |
Yeah... to me it does look like the root cause is that we're trying to hash join / group by / etc a json column. Not to say that it's good. But the cause is (I'm pretty sure) a known issue. We should figure out how to detect this earlier and reject it with a nice error message. Maybe it would be easier to get the optimizer to do that. |
Both queries mentioned in this issue now execute successfully, so I'm closing this issue. |
This doesn't repro locally, so my guess is this is a behavior that, if the distsql proc is scheduled not on the gateway node, it panics like this.
See https://teamcity.cockroachdb.com/repository/download/Cockroach_Nightlies_WorkloadNightly/1580962:id/sqlsmith/setup%3Dempty/setting%3Dno-ddl/1.logs/cockroach.log and #42101
The text was updated successfully, but these errors were encountered: