[SPARK-51391][SQL][CONNECT] Fix SparkConnectClient
to respect SPARK_USER
and user.name
#50159
+15
−8
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 aims to fix
SparkConnectClient
to respectSPARK_USER
anduser.name
for the feature parity with PySpark Connect client.BEFORE

AFTER

Why are the changes needed?
Like
pyspark
,spark-shell
andspark-connect-shell
should have a consistent default user when--user_id
is not given.Does this PR introduce any user-facing change?
Yes, this is a bug fix for feature parity across
Spark Connect
languages.BEFORE (Apache Spark 4.0.0 RC2)
AFTER
How was this patch tested?
Pass the CIs and manual review.
Was this patch authored or co-authored using generative AI tooling?
No.