Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Then I think we should either revert this PR or fix it for spark
interpreter as well. Because spark interpreter is the most important
interpreter of zeppelin IMO.
---
If your project is set up
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
@zjffdu Yes, you are right, with SPARK_HOME/SPARK_SUBMIT it doesn't work.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Sorry for late comment. I was in vacation in the last 2 weeks. I found
this didn't work for spark interpreter. @prabhjyotsingh Did you try it for
spark interpreter and other interpreters ?
---
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Closing this, will open a new one with merge of
https://github.com/apache/zeppelin/pull/1265.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1322
I got following checkstyle error while building source.
```
[INFO] There are 1 checkstyle errors.
[ERROR] NotebookServer.java[1381] (sizes) LineLength: Line is longer than
100
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
@Leemoonsoo yes thats a good suggestion. Let me try and do it.
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Instead of `USE_SSH_IMPERSONATION`, how about let user customize
impersonation method?
For example,
```
ZEPPELIN_INTERPRETER_IMPERSONATION_CMD="su - ${ZEPPELIN_USER_NAME}"
```
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Agreed @echarles, the `doAs` part will be a problem, until
[ZEPPELIN-1340](https://issues.apache.org/jira/browse/ZEPPELIN-1340) is
resolved. Until then for security we may have to run half
Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Btw, for the hadoop case (or spark on yarn case), this PR may give an issue
for `doAs`.
Typically, you configure `hadoop.proxyuser.foo.hosts` and
`hadoop.proxyuser.foo.group`, `foo`
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Sure, In this PR I was only thinking about the otherwise case i.e. in the
environment where hadoop dependencies where not present, and hence start
interpreter as end-web-user.
---
If
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1322
@prabhjyotsingh I agree @echarles's idea. Interpreter tries to find hadoop
dependencies first and if it passes, it uses `doAs`. Otherwise, let's talk
about how to do it. How do you think of
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Yes, you are right, let me do it right away.
---
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
Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/1322
... and make ZEPPELIN-1320 a subtask of ZEPPELIN-1337
?
---
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
Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/1322
To make ZEPPELIN-1337 Umbrella for multiple user support for zeppelin more
readable, should we rename the following:
- ZEPPELIN-1340: "Run Hadoop-based interpreter process on Kerberos as
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
@echarles , Yes agreed, will need to update in doc, and a extra toolbar
near the check box where user can enable User Impersonate.
---
If your project is set up for it, you can reply to
Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Whatever `su` or `ssh` is used, I feel the main trick is the user
provisioning on the host running the interpreter. Until now, the shiro
authentication system had no impact on the user
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
> It's better to use RUNAS ~ and su - ~
@jongyoul How about I make `use RUNAS ~ and su - ~` by default, but if in
`zeppelin-env.sh` a property say `USE_SSH_IMPERSONATION` is set
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1322
If i add one more,
What do you guys think about adding an option `Impersonate` in the
interpreter setting on GUI?
That'll give user flexibility of selecting current behavior
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1322
@prabhjyotsingh Without issues above, Could you check this PR support
`scoped` as well which uses multiple threads in one process?
---
If your project is set up for it, you can reply to this
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1322
@prabhjyotsingh I don't know how to support different users' environments
fully, actually. But I think it's better to use `RUNAS ~` and `su - ~` and
using `ssh` without password make some
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
Yes, I thought about the usage in mac and windows, and initially started of
with using `RUNAS ${userName}` for windows and `su - ${userName}` for *nix
systems, but then it requires
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1322
I agree that it's simple way to use ssh to support impersonation. but I'm
worried about it. First, we should consider not to use ssh server in a local
machine. It's disabled on Mac by default
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1322
CI green! Ready for review.
---
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
23 matches
Mail list logo
