[SPARK-46677][CONNECT][FOLLOWUP] Convert count(df["*"])
to count(1)
on client side
#44752
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?
before #44689,
df["*"]
andsf.col("*")
are both convert toUnresolvedStar
, and thenCount(UnresolvedStar)
is converted toCount(1)
in Analyzer:spark/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
Lines 1893 to 1897 in 381f369
in that fix, we introduced a new node
UnresolvedDataFrameStar
fordf["*"]
which will be replaced toResolvedStar
later. Unfortunately, it doesn't matchCount(UnresolvedStar)
any more.So it causes:
which should be
In vanilla Spark, it is up to the
count
function to make such conversionsf.count(df1["*"])
->sf.count(sf.lit(1))
, seespark/sql/core/src/main/scala/org/apache/spark/sql/functions.scala
Lines 422 to 436 in e8dfcd3
So it is a natural way to fix this behavior on the client side.
Why are the changes needed?
to keep the behavior
Does this PR introduce any user-facing change?
it fix a behavior change introduced in #44689
How was this patch tested?
added ut
Was this patch authored or co-authored using generative AI tooling?
no