Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/681#issuecomment-183988935
Regarding portability of notebook authorization permission,
Thanks for creating https://issues.apache.org/jira/browse/ZEPPELIN-666. I
think it make sense to handle as a separate issue. but while we want to
minimize incompatibility of notebook format every release, I think ZEPPELIN-666
must be resolved before the next release.
Regarding authorizing interpreter, it is a good idea.
But to do that, Zeppelin should provide per user interpreter-binding, as a
precondition. Therefore it'll bring much more codebase change and
incompatibility of conf/interpreter.json. So, I think it's nice subject to have
discussion in a separate issue.
Regarding independent notebook structure per user,
I think it's conflict with this Authorization implementation. Because this
design allows multiple owner, and it's not clear how multiple owner can be
handled in 'independent notebook structure per user'.
And this subject is also related to API of NotebookRepo interface, as well
as migration of old directory format issue. I think this is also a subject can
be discussed in a separate issue.
This PR brings note.json structure change. While we don't want to have
incompatible notebook format every version, i think ZEPPELIN-666 need to be
discussed before this PR merge (or at least before the next release) so we can
at least know our direction.
Two other subjects (authorizing interpreter, independent notebook
structure) are able to do as a additional work.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
