Changed behaviour for MV with incorrect select between old and new analyzer about clickhouse HOT 3 CLOSED

The new analyzer forbids invalid queries. See PR with documentation: #64643.

from clickhouse.

I'm doing some tests to ensure that things are compatible in the following corner cases:

• Create a bad MV without the analyzer. Restart with the analyzer. Works fine.
• Create a bad MV on cluster (replicatedmergetree, atomic databases) (analyzer on in both, off in both, on vs off, off vs on)
• Create a bad MV on replicated database (analyzer on in both, off in both, on vs off, off vs on)

Basically verify that independently on the settings (as long as analyzer is set to some value), things will be consistent (fail everywhere or work everywhere).

from clickhouse.

1. Worked fine. The server starts without problems.
2. If you attempt to create the MV ON CLUSTER in the server where the analyzer in on, you get ILLEGAL_TYPE_OF_ARGUMENT and the view is not created anywhere. If you attempt to create it in the server with the analyzer is off, it's created in both servers (no matter if the other server has it on or off).
3. Same behavior with the Replicated database engine. Analyzer=0 allows the creation (and it will propagate correctly), while analyzer=1 will prevent it.

So everything is working as expected.

from clickhouse.