For issue (1) you might want to try Amazon EFS. While EFS is designed for “big
data”, you can use it for other concurrency use cases. You need to pay very
close attention to your storage size/utilization ratios as EFS can complete
choke off bandwidth. I would also look at using EFS for Noteboo
Zhang
Reply-To: "users@zeppelin.apache.org"
Date: Tuesday, October 17, 2017 at 1:07 AM
To: "users@zeppelin.apache.org"
Subject: Re: notebook-authorization.json file makes Zeppelin not scalable
Unify storage could be done in 0.8.0. But for your scenario, it's not about
s
es Zepplin 0.8.0-SNAPSHOT MONGO DB store
> autorizations in db or still in that json file?
>
>
>
> *From: *Jeff Zhang
> *Reply-To: *"users@zeppelin.apache.org"
> *Date: *Tuesday, October 17, 2017 at 12:28 AM
> *To: *"users@zeppelin.apache.org"
ubject: Re: notebook-authorization.json file makes Zeppelin not scalable
Still in file format.
Tan, Jialiang mailto:j...@ea.com>>于2017年10月17日周二 下午3:38写道：
Thanks for such quick reply. Does Zepplin 0.8.0-SNAPSHOT MONGO DB store
autorizations in db or still in that json file?
From: Jeff Zha
ate: *Tuesday, October 17, 2017 at 12:28 AM
> *To: *"users@zeppelin.apache.org"
> *Subject: *Re: notebook-authorization.json file makes Zeppelin not
> scalable
>
>
>
>
>
> There's one ticket for unifying zeppelin storage layer.
> https://issues.apache
k-authorization.json file makes Zeppelin not scalable
There's one ticket for unifying zeppelin storage layer.
https://issues.apache.org/jira/browse/ZEPPELIN-2742
But for your case about sharing notebook-authorization across multiple zeppelin
instances, I think this ticket is not enough, i
There's one ticket for unifying zeppelin storage layer.
https://issues.apache.org/jira/browse/ZEPPELIN-2742
But for your case about sharing notebook-authorization across multiple
zeppelin instances, I think this ticket is not enough, it would require
more deep integration with shiro's authorizatio
