Using Authentication in Zeppelin, you can set Read/Write rules to Notebooks
On Thu, Jun 16, 2016 at 10:29 PM, ashish rawat <dceash...@gmail.com> wrote: > Yeah, I thought the same, but this is quite unmanageable for a changing > dashboard and changing user list. > > Perhaps, a clean solution could be to introduce a read mode, where the > notebook is maintained per user session and changes are only kept in memory > and not persisted. > > If there are no solutions out-of-the-box, I would try this out. > > Regards, > Ashish > On Jun 16, 2016 4:40 PM, "Darren Govoni" <dar...@ontrenet.com> wrote: > > I guess the workaround is to copy the notebook for each user. Simplest > solution. > > > > Sent from my Verizon Wireless 4G LTE smartphone > > > -------- Original message -------- > From: ashish rawat <dceash...@gmail.com> > Date: 06/16/2016 6:54 AM (GMT-05:00) > To: us...@zeppelin.incubator.apache.org > Subject: Zeppelin multi-user dashboards > > Hi All, > > I believe there has been some work done on multitenancy in Zeppelin > through z-manager, but that does not look aligned with a typical dashboard > use case, where once a Dashboard/Notebook gets created, multiple users > login and use the dashboard by changing various filters. > > In case of a Zeppelin notebook, when two users work on the same notebook > and change selectors and input boxes, the changes are immediately visible > to any other user who is using the same notebook. This creates problem in > paralleling analysing data using the same notebook. > > Is there any workaround to this issue, with core zeppelin or z-manager? > > Regards, > Ashish > >
