-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Error with enable new analyzer: "Not found column __table1.name in block" #63395
Comments
Please provide a reproducer, version used, etc. This works fine:
|
Strange behaviour:
but if its not changed and default config, its throw error
|
Are you using a cluster where the replicas have different CH versions and different settings for |
with same default config in both servers its work. Seems problem only when its not the same on all servers. |
You must setup the same config in both servers or explicitly enable the setting (via config or query) in the initiator. |
Its okey, but maybe should add more friendly error, for this case. Its not obvious at all, and its can be easy to forgot to change and sync it on all servers in first time. |
With enabled new analyzer( allow_experimental_analyzer = 1), queries start not work with exception
DB::Exception: Not found column __table1.name
The text was updated successfully, but these errors were encountered: