-
Notifications
You must be signed in to change notification settings - Fork 7k
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
[Exception] DB::Exception: Block structure mismatch in UNION stream: different number of columns #2156
Comments
Can you try to create an example how to reproduce this problem? |
@KochetovNicolai, here are demo, you can try. if the query with
|
@lamber-ken, thank you for demo. I've reproduced on cluster with 2 shards. |
@KochetovNicolai , it seems dosn't been fixed, version 1.1.54378
|
This is also happening for me on 1.1.54381 |
This is still happening for me on 1.1.54388 :( |
I have the same or a similar issue on 1.1.54388
Replacing the where condition with a between (or just end to the interval) make it works...
Maybe that help to understand where is the issue. |
This post seems related and add some info: |
The same for LIMIT on FINAL query for ReplicatedCollapsingMergeTree SELECT * FROM table_name FINAL LIMIT 1
The column which it shows different is cityHash64(column) which is used in a tuple expression for the collapsing (primary key). |
Sorry, the previous message is related to Distributed on ReplicatedCollapsingMergeTree. |
Same problem with latest stable version 18.12.14, 18.12.17 steps to reproduce:
test with nodata
|
I reproduce same issue on 18.14.9 version with select query . Error: But removing the limit section make it works. |
Fixed in master. |
When trying to perform a UNION ALL, I'm getting this error:
Both tables have the same size in columns (10), data types and column names are all the same. Tried casting all columns toString() as Concat() only concats strings and got the same error. The error message isn't very helpful. Ideas on how to troubleshoot? |
@raulgregg could you please, open a separate issue? |
I have the same problem. version 20.5.2.7 (official build)
My query looks like:
results_v1 and correctives_v1 have identical structure |
@KochetovNicolai Hello, I just opened a issue #13936 |
env
centerlog
is a distributed tabletable structure
select some field, throw error
select asterisk *, no problem
The text was updated successfully, but these errors were encountered: