Hi Moon/Hyoungjun Kim, I've created the ticket and have put in the description - https://issues.apache.org/jira/browse/ZEPPELIN-385. I'm of the opinion that this will be a useful feature even after the notion of users is introduced. Sharing & Collaboration in the long term could also mean sharing directly the data-set that results from the analysis with a way of loading it, instead of running the same scripts again.
Thanks, Rohit. On Mon, Nov 2, 2015 at 8:41 PM, moon soo Lee <[email protected]> wrote: > Hi Hyoungjun Kim, > > Thanks for sharing your work. Checked your code and looks interesting. > Please free to create Issue/PR about it, if you don't mind. :-) > > Thanks, > moon > > > On Thu, Oct 29, 2015 at 1:11 AM Hyoungjun Kim <[email protected]> wrote: > > > Hi All, > > > > I use Zeppelin to analyze our service log data. Usually developer or team > > uses Zeppelin but sometime planning team or other team want to see the > > result of the analysis. > > So I am trying to share some notebooks with other teams but not > developer. > > Currently Zeppelin doesn't support the access control feature. I think it > > will take long time to implement that feature. > > If I open Zeppelin web page to others, anyone can change a notebook and > > execute it. To prevent modify notebook, I made a readonly Zeppelin > version. > > With this version, if you set 'zeppelin.server.readonly' property, the > > following features are disabled in Zeppelin web page. > > > > - Interpreter setting. > > - Create new notebook. > > - Change notebook name. > > - Show/Hide the code. > > - Show/Hide the output. > > - Remove the notebook. > > - Clone the notebook. > > - Run scheduler. > > - Set each paragraph. > > - Edit paragraph. > > - Edit paragraph title. > > > > You can download this version with the following link: > > https://github.com/babokim/incubator-zeppelin/tree/readonly > > > > I don't know Zeppelin community wants this feature. If the community > wants > > this feature, I will request merge. Please let me know. > > > > Thanks. > > > > Best regards, > > Hyoungjun Kim. > > >
