Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1265
About the first comment you should set `scoped` or `isolated`, not
`shared`. And growth of complexity is to remain backward compatibility. I
also agree that interpreter setting become too many. But if we may break
the current behaviour, we should discuss first and then change it. To make
that setting global is more easier than now, but we should try to reduce
the change when users upgrade Zeppelin.
On Friday, 2 September 2016, Jeff Zhang <notificati...@github.com> wrote:
> Besides I have other 2 concerns.
>
> -
>
> I am a little confused about the combination of the interpreter
> options. There's so many combinations (2*2*3=12), I am not sure
> whether users are comfortable with that.
>
> [image: image]
>
<https://cloud.githubusercontent.com/assets/164491/18192968/84a5d8ca-710b-11e6-8a29-10109bd3692b.png>
> -
>
> Is it necessary to apply this feature globally ? For now it seems
> spark interpreter is the only one that needs it as we want each user
has
> his own SparkContext. I don't see the necessary that other interpreter
> needs that. (At least it is not necessary for livy, as livy interpreter
> will create spark session per user)
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/zeppelin/pull/1265#issuecomment-244283197>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/ADcflrRQnTCuZY6YnoSzlp_XR8OCEmulks5ql6xngaJpZM4Jauiv>
> .
>
--
ì´ì¢
ì´, Jongyoul Lee, æå®ç
http://madeng.net
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
