Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1265
Thanks @jongyoul , change it to `isolated` works.
Regarding the option complexity, I still have concern on that. So now
there's 2 dimensions for interpreter (user/note) IIUC. Before 0.6, zeppelin
don't support shiro and it makes sense to take note as the dimension. I guess
the reason we introduce `shared`, `scopes`, `isolated` is because at that time
we don't have shiro, but we want to control whether to share or isolate
SparkContext between users. so we introduce `shared`, `scopes`, `isolated` to
achieve that. But after 0.6, zeppelin support shiro, I think it is more proper
to take user as the first dimension (maybe remove note dimension later).
By default each user should run his own interpreter, I think this is the
most often used scenarios. For the scenario of `collaborative analysis`, I
would suggest user to create a new interpreter with option `shared` and set
permission on that interpreter to control who can share this interpreter across
users.
Overall, my concern is to reduce complexity. Since zeppelin is a tool and
bridge between user and spark(other interpreter). The goal of zeppelin is to
make the life of analyst easier, we should add less complexity as possible on
the user facing UI. I know break compatibility is bad for user, but complexity
is also very bad to users, we should balance them.
**Besides, I think we should think more deeply on the relationship between
note, user and interpreter.**
---
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.
---
