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
Different results are returned at every execution by executing same query which contains several UNIONs and JOINs in version 20.3.3. #9826
Comments
@KochetovNicolai can you check it is not related to processors? @lu-yuki-matsumoto Can you check that it is reproducing even with |
I checked the query with Thank you, |
Hi @lu-yuki-matsumoto Could you please show me the whole query and Or, probably, find a smaller reproducible example (like, create some tables and insert toy data into them). |
Things I tried:
Still can't reproduce. |
I'm sorry to be very late.
|
@lu-yuki-matsumoto thank you. I still can't reproduce the issue on my artificial generated data.
It will help me a lot if you do anything of that. |
I should apologize for you about mistake I made in my query. Below query can reproduce only case of returning 7 values.
|
@lu-yuki-matsumoto thank you so much! |
Overview
Different results are returned as result of executing the same query which commands joining several tables and union each tables.
Sometimes results of executing the query lacking some joined tables.
When I execute it several times, joined tables which are heavier and/or in latter position of query are lacked in more trial.
It seems that a bug occurs on executing parallel processing, and it maybe union executing before fetching all intermediate tables.
This occurs on clickhouse version20.3.3.
How to Reproduce
I execute below query.
This query is expected returning 8 tableNames, but it returns different number of tableNames at every execution.
Executing Query
Testing and consideration
I executed the query 100 times and counted values in tableName rows.
*When executing alone, queryNotJoin, queryFilteredBeforeJoin and queryFilteredAfterJoin are spent less time in this order.
Comparing same joined table query, result of in latter position of query result is more lacked.
Comparing different joined table query, result of slower query is more lacked.
I guess that this problem is caused by that the UNION is executed without waiting to done processes of fetching joined table.
The text was updated successfully, but these errors were encountered: