Alexey MilovidovandClaude Opus 5.5 71b03103a5 Remove enable_analyzer and allow_experimental_analyzer from tests ...

The old query analysis was removed, and `enable_analyzer` (canonically
`allow_experimental_analyzer`) is an obsolete setting frozen at `1`, so setting
it in tests does nothing. Remove it from stateless, integration, performance and
SQLStorm tests: drop `SET` statements, `SETTINGS` items, client options, loops
over both values and their echoed labels, and comments explaining why the
setting was pinned.

Tests of the obsolete setting itself are kept as they are:
`05136_analyzer_cannot_be_disabled`, `05210_analyzer_cannot_be_disabled_by_query_kind`,
`05292_analyzer_setting_float_value`, `04348_query_parameter_name_collides_with_setting`,
`04078_settings_constraints_compatibility_const`, `05099_client_options_exact_lookup`,
`03999_settings_history_baseline` and the `test_analyzer_compatibility` integration
test, which runs an old server version that still honours the setting.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 03:47:40 +00:00

..

rewrite_queries.py

Address review: leave UNNEST(...) WITH ORDINALITY unchanged in arrayJoin rewrite

2026-06-19 16:24:04 +00:00

runner.py

Remove enable_analyzer and allow_experimental_analyzer from tests

2026-10-16 03:47:40 +00:00

test_rewrite_queries.py

Address review: leave UNNEST(...) WITH ORDINALITY unchanged in arrayJoin rewrite

2026-06-19 16:24:04 +00:00