Hi All, I have the same requirement as that of Ashish, wherein the same Dashboard will be used by multiple users and each user will look at the charts by applying different filters. Can somebody from the core Zeppelin team provide the right way to have this feature built in Zeppelin?
Regards, Skanda On Thu, Jun 23, 2016 at 2:24 PM, Andrea Santurbano <sant...@gmail.com> wrote: > As Ashish said: > > *For Zeppelin, this is true that if the view is different from each user, > then it is not the same notebook anymore. But from a dashboard perspective, > multiple users work on the same dashboard, viewing different data and we > still call it the same dashboard.* > > This is a common use case in most of organizations. We need to find a way > in order to make it work. > There is someone on zeppelin core team that can answer or give a hint on > that? > > Il giorno ven 17 giu 2016 alle ore 10:10 Corneau Damien < > cornead...@gmail.com> ha scritto: > >> That's why I was talking about easy way VS more complicated changes. >> The idea behind the easy way was to bypass the server save and send the >> result to the view directly. >> >> Honestly, I'm not knowledgeable enough to give an estimation of how hard >> caching of previous results, or other methods would be. >> >> >> >> On Fri, Jun 17, 2016 at 5:04 PM, ashish rawat <dceash...@gmail.com> >> wrote: >> >>> Yes, that looks like a good way to do it. Also, you mentioned an >>> important point that user would have to stay on the page for query to >>> finish and the results would be flushed when moving to a new page. This is >>> typically the case in dashboard that queries have very small response times >>> and users wait for the results. But still, as per my understanding, >>> dashboards do retain the last viewed data (through browser cache) and also >>> allow people to navigate to some other screen while the data is getting >>> loaded. >>> >>> Is there any limitation in Zeppelin, which would not let browser cache >>> the view for the current user session? Is it because Zeppelin web always >>> asks for a fresh copy of the notebook from server, whenever user switches >>> notebooks? Perhaps, keeping the changed state of the notebook in the user >>> session at the server side might resolve this? >>> >>> Regards, >>> Ashish >>> On Jun 17, 2016 1:09 PM, "Corneau Damien" <cornead...@gmail.com> wrote: >>> >>> The easy way to do that would be: >>> Have an option on the notebook (automatic-save vs manual save), manual >>> save could be set as an Admin command only, and once activated any change >>> on the notebook wouldn't be propagated to others or saved in the note.json >>> >>> One drawback however would be that you would be forced to stay on the >>> page until the query is finished, and the modification would be flushed >>> once you visit a different page. >>> >>> Otherwise, it would probably need some heavy changes to the Notebook >>> Repo and saving mechanism etc... >>> >>> >>> >>> On Fri, Jun 17, 2016 at 4:14 PM, ashish rawat <dceash...@gmail.com> >>> wrote: >>> >>>> Thanks Vincent. I haven't explore git storage much, but it's important >>>> for us that the cost the maintaining a changing notebook and a changing >>>> user list shouldn't be high. If we have 20 dashboard users and there are >>>> minor changes in dashboard functionality every two weeks, then there should >>>> not be a need to make changes to all the 20 copies manually. Apart from >>>> taking time, this would invariably result in some human error and >>>> variations in copies of the same notebook. Moreover maintaining user >>>> permissions, also become complex with so many copies. >>>> >>>> The overall user management and authorization may become non-trivial to >>>> manage if we start creating copies for what should be just one notebook. >>>> >>>> Regards, >>>> Ashish >>>> >>>> On Fri, Jun 17, 2016 at 11:37 AM, vincent gromakowski < >>>> vincent.gromakow...@gmail.com> wrote: >>>> >>>>> Isnt it acheivable via git repository ? A kind of git clone to get an >>>>> indépendant copy of the notebook? >>>>> Le 17 juin 2016 4:18 AM, "Corneau Damien" <cornead...@gmail.com> a >>>>> écrit : >>>>> >>>>>> It is simple Read/Write >>>>>> Some people can edit, some people can see. >>>>>> >>>>>> By essence, if the view is different from each user, then it is not >>>>>> the same notebook anymore. >>>>>> Being able to have a different results for each user saved somewhere >>>>>> so that they can read it, seems like a big overhead. >>>>>> >>>>>> On Fri, Jun 17, 2016 at 6:35 AM, ashish rawat <dceash...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Damien, >>>>>>> >>>>>>> Does the read mode work as I described above i.e. multiple users can >>>>>>> work with selectors and input boxes of the same notebook and view >>>>>>> different >>>>>>> outputs? >>>>>>> My assumption is that read will only allow users to just view the >>>>>>> notebook in report mode and not interact with it, perhaps an >>>>>>> interactive-read is required for a typical dashboard use case. >>>>>>> >>>>>>> Regards, >>>>>>> Ashish >>>>>>> >>>>>>> On Thu, Jun 16, 2016 at 7:51 PM, Corneau Damien < >>>>>>> cornead...@gmail.com> wrote: >>>>>>> >>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>> >>> >>
