Hi Jagat,
I'd love to listen how users use Apache Zeppelin in real world. It always
help to figure out what we have to focus on, to find out what the critical
issues are and to set the future roadmap. Can you share us - or me - detail
issues bothering you?
On Wed, Feb 22, 2017 at 5:28 PM, Jagat S
We are implementing the exact same use case today , Trying out central
shared zeppelin 0.7 instance in our organisation.
As member of admin team we have locked down the interpreter page and
published set of settings which we have been configured in the backend.
If Interpreter settings are per use
Yes, we can set some roles by Shiro but what I mean is we didn't implement
role-based functions like hiding or showing some menu.
On Thu, Feb 23, 2017 at 12:17 PM, Prabhjyot Singh wrote:
> Yes, agreed we need some components to manage lifecycle of interpreters.
>
> > "I agree that we need to ke
Yes, agreed we need some components to manage lifecycle of interpreters.
> "I agree that we need to keep same behavior even though users restart in
any place."
I too agree we should have same behaviour.
> Thus we must not assume that "admin" exists.
In Zeppelin we can do this
https://github.com
Basically, I agree that we need to keep same behavior even though users
restart in any place. I don't have any preference between restarting all
processes and starting user's process but currently Zeppelin doesn't have
any "admin" feature and no concept like admin by default. Thus we must not
assum
I think we can combine scenario 2 and 3 if user click yes button on the
popup window of whether you want to restart interpreter in scenario 3.
Regarding the restarting scenario of 1,2,3, IMHO I think we don't need to
differentiate them. Otherwise it might confuse users that restarting in
different
This is WRT the PR that I've created
https://github.com/apache/zeppelin/pull/2034.
The issue that I want to discuss over here is how should an Interpreter
behave when it is;
- restarted from notebook
- restarted from Interpreter setting page
- edited from Interpreter setting page
- deleted fro
