MoanasDaddyXu opened a new issue, #65388: URL: https://github.com/apache/doris/issues/65388
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/doris/issues) and found no similar issues. ### Version Reproduced with the table stream regression case on local Doris HEAD `d4a077caf8a`. Test environment: ```text regression-test/suites/table_stream_p0/test_table_stream_alter_comment.groovy remote log: /mnt/disk1/jianxu/case_output/doris/testrun/table_stream_p0_20260708/test_table_stream_alter_comment.retry2.log FE: 172.20.49.4:9030 ``` ### What's Wrong? `ALTER STREAM ... SET COMMENT` fails at parser stage, even though table stream creation with an initial comment works and `information_schema.table_streams` exposes the comment. Failing SQL: ```sql ALTER STREAM s_alter_comment SET COMMENT 'updated comment'; ``` Actual error: ```text errCode = 2, detailMessage = no viable alternative at input 'ALTER STREAM'(line 1, pos 6) ``` ### What You Expected? `ALTER STREAM ... SET COMMENT` should be parsed and executed successfully, and `information_schema.table_streams.STREAM_COMMENT` should reflect the updated comment. ### How to Reproduce? Regression case: ```text regression-test/suites/table_stream_p0/test_table_stream_alter_comment.groovy ``` Minimal flow: ```sql CREATE TABLE base_dup ( k1 INT, v1 INT ) DUPLICATE KEY(k1) DISTRIBUTED BY HASH(k1) BUCKETS 1 PROPERTIES ( "replication_num" = "1", "binlog.enable" = "true", "binlog.format" = "ROW" ); CREATE STREAM s_alter_comment ON TABLE base_dup COMMENT 'initial comment' PROPERTIES ("type" = "append_only"); ALTER STREAM s_alter_comment SET COMMENT 'updated comment'; ``` ### Regression Test Result ```text suite: test_table_stream_alter_comment command: ALTER STREAM s_alter_comment SET COMMENT 'updated comment' actual: no viable alternative at input 'ALTER STREAM'(line 1, pos 6) ``` ### Anything Else? Tracking issue: #65265 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! -- 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]
