[SPARK-56999][CONNECT] Propagate Spark Connect session user as a SparkContext local property#55917
Open
hit2024 wants to merge 1 commit into
Open
[SPARK-56999][CONNECT] Propagate Spark Connect session user as a SparkContext local property#55917hit2024 wants to merge 1 commit into
hit2024 wants to merge 1 commit into
Conversation
…kContext local property
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Propagating Spark Connect session user as a SparkContext local property. Currently user is added to the job description and not as a separate SparkContext property.
Why are the changes needed?
We use SparkConnect along with Ranger for RBAC (org.apache.kyuubi.plugin.spark.authz.ranger.RangerSparkExtension), which requires the user (currently it checks for "kyuubi.session.user", will add a fallback to check for "spark.connect.session.user")
Does this PR introduce any user-facing change?
No
How was this patch tested?
Tested it on local where the RangerSparkExtension was able to extract the user as expected. No tests were added because its a small, trivial and non-destructive, backward compatible new feature.
Was this patch authored or co-authored using generative AI tooling?
No