[SPARK-32344][SQL][2.4] Unevaluable expr is set to FIRST/LAST ignoreNullsExpr in distinct aggregates #29157
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?
This PR intends to fix a bug of distinct FIRST/LAST aggregates in v2.4.6;
A root cause of this bug is that the
Aggregationstrategy replaces a foldable booleanignoreNullsExprexpr with aUnevaluableexpr (AttributeReference) for distinct FIRST/LAST aggregate functions. But, this operation cannot be allowed because theAnalyzerhas checked that it must be foldabe;spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/First.scala
Lines 74 to 76 in ffdbbae
So, this PR proposes to change a vriable for
IGNORE NULLSfromExpressiontoBooleanto avoid the case.This is the backport of #29143.
Why are the changes needed?
Bugfix.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added a test in
DataFrameAggregateSuite.