[SPARK-34012][SQL][3.0] Keep behavior consistent when conf spark.sqllegacy.parser.havingWithoutGroupByAsWhere
is true with migration guide
#31049
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 #22696 we support HAVING without GROUP BY means global aggregate
But since we treat having as Filter before, in this way will cause a lot of analyze error, after #28294 we use
UnresolvedHaving
to insteadFilter
to solve such problem, but break origin logical about treatSELECT 1 FROM range(10) HAVING true
asSELECT 1 FROM range(10) WHERE true
.This PR fix this issue and add UT.
NOTE: This backport comes from #31039
Why are the changes needed?
Keep consistent behavior of migration guide.
Does this PR introduce any user-facing change?
No
How was this patch tested?
added UT