[SPARK-54871] [SQL] Trim aliases from grouping and aggregate expressions before handling grouping analytics #53644
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What changes were proposed in this pull request?
In this PR I propose to trim aliases from grouping and aggregate expressions before handling grouping analytics. This is needed for the following query:
Here we have
col1in the single-pass whereas in the fixed-point we havecol1 AS k2before constructing anAggregateinResolveGroupingAnalytics. Change removes theAS k2part and keeps the compatibility between single-pass and fixed-point analyzers without changing outputs (analyzed plans are different, only names).The change also inlines the behavior with regular aggregates (without grouping analytics). In other words:
Here
col1 + col2should be the grouping expression (as it is) and we inline the behaviors.Why are the changes needed?
To keep the compatibility between fixed-point and single-pass analyzers.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Changed tests.
Was this patch authored or co-authored using generative AI tooling?
No.