You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 42f8f2e
Browse filesBrowse the repository at this point in the historyBrowse files
[improvement](ddl) Restrict state types to aggregate tables (#66963)
### What problem does this PR solve?
Issue Number: close#65865
Related PR: #66664
Problem Summary: HLL, QUANTILE_STATE, and AGG_STATE columns in
non-aggregate table models can enter row conversion paths that do not
support nullable aggregate-state values and fail at runtime. Reject new
definitions of these types in Duplicate Key and Unique Key tables by
default, while retaining a temporary FE compatibility switch for
migration. Existing Aggregate Key tables remain supported.
### Release note
HLL, QUANTILE_STATE, and AGG_STATE columns are restricted to Aggregate
Key tables by default. The temporary FE config
`enable_non_aggregate_table_state_types=true` can restore the previous
definition behavior during migration and will be removed after the
compatibility transition period.
### Check List (For Author)
- Test: Unit Test / Build
- `./run-fe-ut.sh --run
org.apache.doris.nereids.trees.plans.commands.info.ColumnDefinitionTest`
- `./build.sh --fe`
- `./build.sh --be`
- Regression test added but not run because an isolated cluster rebuild
requires separate destructive-action approval
- Behavior changed: Yes. New HLL, QUANTILE_STATE, and AGG_STATE columns
are rejected in non-Aggregate Key tables by default
- Does this need documentation: No. The compatibility switch is
temporary and carries its removal notice in the FE config description
0 commit comments