morrySnow opened a new pull request, #66951:
URL: https://github.com/apache/doris/pull/66951

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: None
   
   Problem Summary: The `primaryExpression` rule encoded CASE and CONVERT 
branches with repeated prefixes, split query and expression parentheses into 
competing alternatives, and represented array access, dereference, and COLLATE 
through direct left recursion. This change factors the rule into a primary base 
plus ordered postfix suffixes, consolidates the shared prefixes, and folds 
suffixes left-to-right in the FE visitor. It preserves SQL AST semantics, 
invalid-input positions, and Create View source intervals while allowing the 
independent parser CST to change.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test
     - [ ] Regression test
     - [x] Unit Test
     - [ ] Manual test
     - [ ] No need to test or manual test
     - `./run-fe-ut.sh --run 
org.apache.doris.sqlparser.DorisSqlParserTest,org.apache.doris.sqlparser.PrimaryExpressionTest,org.apache.doris.nereids.parser.PrimaryExpressionAstTest,org.apache.doris.nereids.parser.NereidsParserTest,org.apache.doris.nereids.trees.expressions.ExpressionParserTest,org.apache.doris.nereids.parser.LimitClauseTest`
     - `mvn checkstyle:check -pl fe-core,fe-sql-parser`
     - `DISABLE_BUILD_UI=ON MVN_OPT=-Dmaven.build.cache.enabled=false 
./build.sh --fe --output <fresh-output-dir>`
   - Behavior changed:
     - [x] No.
     - [ ] Yes.
   - Does this need documentation?
     - [x] No.
     - [ ] Yes.
   


-- 
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