| CREATE (OR REPLACE)? VIEW qualifiedName        columnComments?        (COMMENT string)?        (SECURITY (DEFINER | INVOKER))?        (WITH properties)? AS rootQuery                                #createView        columnComments    : '(' columnComment (',' columnComment)* ')'    ;columnComment    : qualifiedName (COMMENT string)?    ;

So we can create view with column alias and comment as follow:

CREATEVIEWtest (id COMMENT'id', name COMMENT'name')ASSELECT123 ,'456';CREATEVIEWtest (id COMMENT'id', name COMMENT'name')ASSELECT123as id ,'456'as id;

AndSHOW CREATE VIEW will expose these column alias and comment. The behavior of the existingCREATE VIEW syntax remains unchanged which will not expose them.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(X) Release notes are required, with the following suggested text:

##General* Add support for column aliases and comments in`CREATE VIEW` statements. ({issue}`issuenumber`)

cla-botbot added the cla-signed label

Dec 17, 2025

hqbhoho marked this pull request as draft

December 17, 2025 10:24

hqbhoho force-pushed thefeat/support_create_view_with_comment branch frome6014af tof036403Compare

December 17, 2025 10:51

hqbhoho marked this pull request as ready for review

December 17, 2025 10:52

raunaqmorarka added the syntax-needs-review label

Dec 17, 2025

raunaqmorarka requested review fromPraveen2112,ebyhr,kasiafi andmartint

December 17, 2025 15:44

Copy link

Member

ebyhr commentedDec 18, 2025

The logic around duplicate column names handling looks wrong. The below CRATE VIEW should fail:

CREATEVIEWduplicate_columns (regionkey, regionkey2)ASSELECT regionkey, regionkeyFROM region;TABLE duplicate_columns;line1:1: View'memory.default.duplicate_columns' is staleorin invalid state: column [regionkey] of typebigint projectedfrom query view at position1 has a different namefrom column [regionkey2] of typebigint storedin view definition

hqbhoho marked this pull request as draft

December 18, 2025 03:11

Copy link

ContributorAuthor

hqbhoho commentedDec 18, 2025•
edited
Loading

@ebyhr Thanks for your feedback
The same SQL query that fails with aDuplicate column name error in Hive but executes successfully in StarRocks.
Currently, there is indeed an issue: if the aliased column name does not match the name defined in the query, it will cause an execution error when query this view.
What I'd like to confirm is, if we support aliased columns in views, can we then allow duplicate column names in a query?