GitHub user sadhen reopened a pull request:
https://github.com/apache/zeppelin/pull/2539
[ZEPPELIN-2863] change notebook-authorization.json and interpreter.json to
NotebookDir
### TODO
+ [ ] Fix travis
### What is this PR for?
When dockerizing Zeppelin, we need to persist the mutable part of Zeppelin
on storage out of docker (for example NFS).
For this reason, notebook-authorization.json and interpreter.json should be
persisted in Notebook Dir.
### What type of PR is it?
[Improvement]
### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2863
### How should this be tested?
Minor change, no need to test it.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update?
No
* Is there breaking changes for older versions?
No
* Does this needs documentation?
Yes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wacai/zeppelin ZEPPELIN-2863
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2539.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2539
----
commit 82ec4e0efc49daa60aed9f54bf42ff991a7873f9
Author: å¿å¬ <[email protected]>
Date: 2017-08-15T13:44:47Z
change notebook-authorization.json and interpreter.json to NotebookDir for
dockerization
commit be8877cb4323d8a4e76f4a15ec9675f00396a5f6
Author: å¿å¬ <[email protected]>
Date: 2017-08-16T03:04:14Z
update corresponding comments and configs
commit 9e21f0e2518f1899fbd8c891b89d74ee03b1f9e8
Author: å¿å¬ <[email protected]>
Date: 2017-08-16T03:22:55Z
fix
commit d7a6d71d9af011f9fd2ebf2be813a60b8118924b
Author: å¿å¬ <[email protected]>
Date: 2017-08-16T06:07:39Z
fix unit test
commit c802f2c176a961abc4820dd093e4593de906f117
Author: å¿å¬ <[email protected]>
Date: 2017-08-16T06:29:27Z
fix unit test on NoteInterpreterLoaderTest
----
---
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.
---
