ClickHouse: Do we have some mechanism to ensure that subqueries sent from initial node won't be optimized by rewritten.
Use case
Do we have some mechanism to ensure that subqueries sent from initial node won’t be optimized by rewritten.
This would make sense to reduce the exceptions Not found column
which happened when initial node didn’t optimize by rewritting ast but worker node did it.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (14 by maintainers)
@vdimir I found out why you can’t reproduce. In lastest version of clickhouse, optimize will not be executed on non-initial query, see https://github.com/ClickHouse/ClickHouse/pull/28746/files introduced by @amosbird
@vdimir You should test it in clickhouse cluster with some replicas deployed with old version before the pr which brought
optimize_rewrite_sum_if_to_count_if
, and some deployed with new version after that pr.I tried to add test https://github.com/ClickHouse/ClickHouse/pull/35049 but it’s not fail locally.
@taiyang-li do you have reproducible example?