Could you create ticket for this issue ?

Mor Yariv <m...@nutrinohealth.com> 于2019年5月1日周三 下午9:29写道:

> I am trying to setup zeppelin to work with two synced notebook repos - an
> s3 repo which is our current repo and a github one on top of it to allow
> committing and tagging note versions to git.
> We currently use s3 since we have many local and remote zeppelin instances
> we fire up and shut down constantly, and we want to share our notes between
> all of them. Our zeppelin version is 0.8.1.
>
> When I tried to add the github repo to our setup I ran into one of two
> problems:
> 1. If the zeppelin.notebook.storage setting lists the s3 repo first, the
> revision controls are hidden (because of isRevisionSupportedInDefaultRepo
> in zeppelin-zengine which only checks the first repo for revision support).
> 2. If the setting lists the github repo first, when the server starts up
> only the github notes are loaded and only after the user clicks the refresh
> button to reload notes the sync function is called and the s3 notes are
> added to the list. In NotebookRepoSync's constructor it actually does sync
> the repos, but only if anonymous access is allowed (and I can confirm it
> works in my setup, but we do need to disable anonymous access).
>
> Which (if any) is the best practice for this? What are the reasons for the
> revision support to only work if the first repo supports it and for the
> sync to only happen if anonymous access is enabled?
> For now as a workaround I modified zengine to allow revision support to be
> enabled if either of the repos supports it and it seems to be working fine.
>
>
> Thanks!
> Mor
>
>

-- 
Best Regards

Jeff Zhang

Reply via email to