Revert "Revert "Add a test for #56334""#84143
Conversation
…mismatch-after-metadata-only-alter
…mismatch-after-metadata-only-alter
|
@alexey-milovidov |
…mismatch-after-metadata-only-alter
…mismatch-after-metadata-only-alter
…mismatch-after-metadata-only-alter
|
The introduced test #56334 is still valid issue |
…mismatch-after-metadata-only-alter
…mismatch-after-metadata-only-alter
…r-metadata-only-alter' of github.com:ClickHouse/ClickHouse into revert-84024-revert-84016-block-structure-mismatch-after-metadata-only-alter
…mismatch-after-metadata-only-alter
…projection optimization When using aggregate projection optimization (e.g., minmax_count projection), the projection data may have different types for key columns due to metadata-only ALTERs (e.g., extending an Enum). This caused a "Block structure mismatch" error in `AggregatingStep::requestOnlyMergeForAggregateProjection`. The fix adapts the projection input header to use the expected output types for columns that exist in the output header. This ensures that after `updateOutputHeader()` is called, the output header types match the expected types from the original query. Closes #56334 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
@amosbird, I'm a little bit doubtful about this. Maybe you can take a look. |
I don’t see how this relates to projections in the tests, and I cannot reproduce any failures using fiddle across all major versions since 25.8. |
|
@amosbird the test is intended to run on Debug, ASan, MSan, TSan, UBSan builds. |
It's likely about "virtual projections". |
Reverts #84024
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
After metadata-only ALTERs, such as extending the elements of Enums, the optimization of aggregation with projection may end up producing an exception.