Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1566
So I've done some research and `--proxy-user` argument is used with either
`spark-submit` or `spark-shell` normally, and each of them creates new spark
context. The problem is that Zeppelin calls `spark-submit` only once in
`shared` and `scoped` modes when initializing interpreter, and afterwards
single spark context is used. Thus it makes having impersonation through
`--proxy-user` on spark interpreter in `shared` and `scoped` mode
*complicated*. For isolated mode, it's easier since we can pass user with
SparkConf for each spark context on initialization. any suggestions /opinions
are welcome.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---