Github user cacti77 commented on the issue:
https://github.com/apache/zeppelin/pull/2437
> from the code perspective, there's only one InterpreterGroup for scoped
mode, but multiple sessions in one InterpreterGroup.
If this is true then surely the diagram for scoped mode should only have
one InterpreterGroup in it, but with multiple (Spark?) sessions inside that,
with several interpreters inside each session?
Also, this 'per note' and 'per user' does appear to add another dimension.
So, to explain what's happening you'd need one table for shared/scoped/isolated
for the 'per user' mode and another table again for shared/scoped/isolated for
the 'per note' mode.
It would also be good to have a column or table explaining how data can be
shared, or not, between notebooks in the 3 different modes. As a Zeppelin user
I find all these different combinations really confusing. Maybe an
architectural diagram of how the different parts of Zeppelin talk to each other
would help here. Or maybe the product itself should be simplified to remove a
lot of these combinations, especially if they're not used much?!
---
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.
---
