an issue has been created
https://issues.apache.org/jira/browse/ZEPPELIN-1236
On Mon, Jul 25, 2016 at 9:07 PM Panayotis Trapatsas <
p.trapat...@pamediakopes.gr> wrote:
> +1. Do we have any updates on this issue?
>
> On Thu, Jun 30, 2016 at 10:23 AM, Skanda
> wrote:
>
>> Hi All,
>>
>> I have the
+1. Do we have any updates on this issue?
On Thu, Jun 30, 2016 at 10:23 AM, Skanda wrote:
> 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 f
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,
Ska
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 ca
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.
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
wai
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
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
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.
Essentially, the difference boils down to
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" 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 no
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 1
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 intera
Using Authentication in Zeppelin, you can set Read/Write rules to Notebooks
On Thu, Jun 16, 2016 at 10:29 PM, ashish rawat 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 re
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
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
Date: 06/16/2016 6:54 AM (GMT-05:00)
To: us...@zeppelin.incubator.apache.org
Subject: Zeppelin multi-
15 matches
Mail list logo
