Raúl MarínandClaude Opus 4.7 72efe28e9c Fix downgrade path in test_sparsity_exact_num_defaults_compat ...

Master evolution broke the compat test by adding server-side changes that
prevent 25.12 from starting on data written by the newer binary:
- `system.text_log_0` (and other rotated log tables) gain the `table_readonly`
  MergeTree setting, which 25.12's `MergeTreeSettingsImpl::loadFromQuery`
  rejects as an unknown setting.
- `system.part_log` parts use the `with_types` `SerializationInfo` format that
  gained a top level `propagate_types_serialization_versions_to_nested_types`
  key, which 25.12's `SerializationInfoByName::readJSONFromString` rejects as
  an unknown field.

Neither has anything to do with the compat property this test exercises
(`exact_num_defaults` inside per-column serialization JSON is safe to ignore
under 25.12). Disable all system logs on the test node so no rotated log tables
or system part_log parts get written -- the same pattern as
`test_topk_alpha_map_compatibility`.

Replace the `system.query_log` based `read_rows` check with an `EXPLAIN` scan
for the `Optimized trivial count with sparsity filter` step description, so
the test no longer depends on `query_log`.

Co-Authored-By: Claude Opus 4.7 <[email protected]>

2026-07-06 15:39:27 +02:00

..

configs

Fix downgrade path in test_sparsity_exact_num_defaults_compat

2026-07-06 15:39:27 +02:00

__init__.py

…

test.py

Fix downgrade path in test_sparsity_exact_num_defaults_compat

2026-07-06 15:39:27 +02:00