ixzc opened a new pull request, #4107:
URL: https://github.com/apache/doris-website/pull/4107

   ## Summary
   
   - Clarify nullable modification rules in the Schema Change documentation: 
**NOT NULL → NULL is supported** (heavyweight Schema Change); **NULL → NOT NULL 
is not supported**.
   - Remove the incorrect blanket limitation that all Nullable attribute 
changes are unsupported, which contradicted examples on the same page and 
actual Doris behavior (`Column.checkSchemaChangeAllowed()`).
   - Add an explicit `MODIFY COLUMN ... NULL` example and list NOT NULL → NULL 
under heavyweight Schema Change operations.
   
   ## Motivation
   
   The current Limitations table states:
   
   > Modifying the aggregation type, Nullable attribute, and default value is 
not supported
   
   This is misleading for operators changing columns to nullable (e.g. `MODIFY 
COLUMN col INT NULL`), which triggers a heavyweight Schema Change job and is 
covered by regression tests (`test_alter_table_column_nullable.groovy`).
   
   ## Files changed
   
   - `docs/table-design/schema-change.md` (dev/current, EN)
   - `i18n/zh-CN/.../current/table-design/schema-change.md` (dev/current, ZH)
   - `versioned_docs/version-4.x/table-design/schema-change.md` (4.x, EN)
   - `i18n/zh-CN/.../version-4.x/table-design/schema-change.md` (4.x, ZH)
   
   ## Test plan
   
   - [x] Verified wording against Doris FE source: 
`fe/fe-core/src/main/java/org/apache/doris/catalog/Column.java` 
(`checkSchemaChangeAllowed`)
   - [x] Aligned with existing doc example `MODIFY COLUMN col3 varchar(50) KEY 
NULL`
   - [x] Aligned with regression test 
`regression-test/suites/schema_change_p0/test_alter_table_column_nullable.groovy`
   
   
   Made with [Cursor](https://cursor.com)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to