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 5e47ca8
Browse filesBrowse the repository at this point in the historyBrowse files
[improvement](ddl) Preserve state types in async materialized views
### What problem does this PR solve?
Issue Number: closeapache#65865
Related PR: apache#66664
Problem Summary: Restricting HLL, QUANTILE_STATE, and AGG_STATE columns to Aggregate Key tables also rejected async materialized views whose analyzed query generates an internal Duplicate Key storage column with an aggregate state type. Treat schemas generated by the async materialized view planner as system-generated during column validation, while retaining the restriction for user-created non-Aggregate Key tables. Add coverage that creates an async materialized view with an AGG_STATE result column.
### Release note
None
### Check List (For Author)
- Test: Unit Test / Build
- `./run-fe-ut.sh --run org.apache.doris.mtmv.MTMVPlanUtilTest`
- `./run-fe-ut.sh --run org.apache.doris.nereids.trees.plans.commands.info.ColumnDefinitionTest,org.apache.doris.alter.InternalSchemaAlterTest`
- `./build.sh -j 192`
- Regression tests were not run because no Doris cluster was deployed in this worktree
- Behavior changed: No. This preserves existing async materialized view behavior while keeping the user-facing restriction unchanged
- Does this need documentation: No
0 commit comments