Skip to content

branch-4.1: [fix](fe) Fix alias function with cast outermost expr and reject illegal expressions #63254#63349

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63254-branch-4.1
Open

branch-4.1: [fix](fe) Fix alias function with cast outermost expr and reject illegal expressions #63254#63349
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63254-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #63254

…gal expressions (#63254)

### What problem does this PR solve?

Problem Summary:
1. When an alias function body has a cast as the outermost expression
(e.g., `cast(n as varchar(20))`), AliasUdf.translateToNereidsFunction
attempted to cast the parsed expression to UnboundFunction, causing
ClassCastException. Fixed by changing the unboundFunction field type
from UnboundFunction to Expression so any expression can be stored.

2. Alias functions whose body contains aggregate functions, window
expressions, subqueries, or other non-scalar expressions could be
created successfully, which is incorrect. Added a containsType check in
translateToLegacyExpr that throws AnalysisException("Alias function only
supports scalar functions.") before attempting the legacy translation.

### Release note

Fix alias function creation failure when the outermost expression is a
cast, and reject alias functions containing aggregate/window/subquery
expressions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot requested a review from yiguolei as a code owner May 18, 2026 07:18
@hello-stephen
Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 100.00% (3/3) 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 33.33% (1/3) 🎉
Increment coverage report
Complete coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants