[LIVY-651] Provide a approach to get "owner" inside spark application#216
Open
yantzu wants to merge 4 commits into
Open
[LIVY-651] Provide a approach to get "owner" inside spark application#216yantzu wants to merge 4 commits into
yantzu wants to merge 4 commits into
Conversation
|
This pull request has been automatically marked as stale because it has had no activity for at least 3 months. If you are still working on this change or plan to move it forward, please leave a comment or push a new commit so we know to keep it open. Otherwise, this PR will be closed automatically in about one month. Thank you for your contribution to Apache Livy! |
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?
When impersonation is disabled, hadoop UGI user will always be livy server user, there is no way to get actually owner user in spark application.
This issue is to fix this problem by add a "spark.livy.owner" property to spark context. Spark application code can get this property if needed.
https://issues.apache.org/jira/browse/LIVY-651
How was this patch tested?
Update existing unit test, and test manually.
