Hi Mark,
B. PullRequest-53 is one good option, especially Hayssam is keeping this branch up to date. A. Reverse Proxy + Zeppelin on docker There're some open source implementation you can leverage. e.g. https://github.com/NFLabs/z-manager/tree/master/multitenancy B and A provides slightly different type of support for multiuser. B uses single Zeppelin instance and all user access all interpreter. A uses multiple Zeppelin instance and and each instance is assigned to user. I think you can try anything you think more appropriate for you. I think multiple viewer for a single notebook is different problem. Zeppelin keeps single state per notebook, so notebook can have only one state at a time. I think B or A can not solve it directly. Currently, I think having viewer's own copy of notebook is only way to support it. But providing multiple state in a notebook for multiple viewer is very interesting topic. Thanks, moon On Fri, Dec 4, 2015 at 3:28 AM Mark Luk <m...@juicero.com> wrote: > I understand the issue of multiuser zeppelin had been raised in the past. > > > https://mail-archives.apache.org/mod_mbox/incubator-zeppelin-users/201506.mbox/%3CCAN-e8+a-=e9daJX+FV9Kq8iDZge3rmwstrb-=dwcjypk9yf...@mail.gmail.com%3E > > > To recap the problem, running Zeppelin out of the box means all users are > all working on the same notebook. Any changes made by 1 user will be seen > by others. > > It seems like moon outline 2 potential solutions here > > > > https://mail-archives.apache.org/mod_mbox/incubator-zeppelin-users/201506.mbox/%3ccalf24szmmnm3am4zrfka9yjkxjbnr0ssu0pwgrjgnrwyopq...@mail.gmail.com%3E > > A. Reverse Proxy + Zeppelin on docker. > > B. Shiro security. PullRequest-53 > > > I was wondering what is the current status of these 2 (or other) solutions? > Anything I can use now? > > Another question is that in my particular case, most users are actually only > using Zeppelin to view data. > > I am providing my users with a datepicker widget so that they have the > ability to view data from different periods on the same notebook. However, > because the notebook is shared, the use case of allowing user A to look date > X while user B is currently looking at date Y is not possible. The notebook > will either show date X or date Y. > > Is the solution to my particular multiuser problem the same as the solutions > mentioned before for multiuser? > > thanks > > mark > >
