GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/1840
[ZEPPELIN-1730, 1587] WIP add spark impersonation through --proxy-user
option
### What is this PR for?
This is to add spark impersonation using --proxy-user option. note that it
enables also to use spark impersonation without having logged user as system
user with configured ssh.
### What type of PR is it?
Improvement
### Todos
* [x] - add for *nix
* [ ] - add for windows
* [x] - testing for standalone
* [ ] - testing for yarn mode
### What is the Jira issue?
Directly solves
[ZEPPELIN-1730](https://issues.apache.org/jira/browse/ZEPPELIN-1730) and also
solves [ZEPPELIN-1587](https://issues.apache.org/jira/browse/ZEPPELIN-1587)
according to discussion in #1566 since using `--proxy-user` in `spark-submit`
is preferable method.
### How should this be tested?
1. switch your spark cluster to `per user` and `isolated` mode
2. set up `user impersonation` flag
3. run some job using that spark interpreter
4. spark context should be created with currently logged in user
credentials on behalf of system user
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/khalidhuseynov/incubator-zeppelin
feat/spark-proxy-user
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1840.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1840
----
commit b68a4a06218977d94621ef2bde7506da45f821f9
Author: Khalid Huseynov <khalid...@gmail.com>
Date: 2017-01-04T09:49:24Z
add --proxy-user option for spark
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
