Thanks for starting this thread and I wish I saw this earlier.
I filed https://issues.apache.org/jira/browse/ZEPPELIN-2236 recently and
much of that feature request is applicable in this blog.
>From this JIRA here are some thoughts on what are different areas of
Zeppelin where we can put in acces
I do like the idea of the Admin feature. It complements Multitenancy very
well.
Not every user should be able to change global settings that affect all
users.
Also most of our Zeppelin users have only high-level understanding of Spark
and can only write sql queries. So the admin feature helps with
I think in authenticated mode, admin is necessary. What admin should take
charge can be in the following 4 areas:
1. Interpreter setting. Admin can control a template for each interpreter,
and each user's template extend this base template but can also customize
his own setting. Besides that, ad
We have multiple uses in our organization share same anonymous account, which
will potentially cause the problems, we hope to have true authenticated mode.
thanks
AL
> On Feb 22, 2017, at 9:14 PM, Jongyoul Lee wrote:
>
> Hi folks,
>
> Recently, I've heard some new feature assumed that it nee
