GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/582
ZEPPELIN-543: Storage initialization failure recovery
### What is this PR for?
Handling edge case failures when initializing notebook storage class(es).
### What type of PR is it?
Improvement
### Todos
* [x] - fix repo initialization
* [x] - add different config tests
### Is there a relevant Jira issue?
[ZEPPELIN-543](https://issues.apache.org/jira/browse/ZEPPELIN-543)
### How should this be tested?
There're various test cases (mostly included as unit tests).
One of the test scenarios:
1. in `conf/zeppelin-env.sh` add the following line
```
export
ZEPPELIN_NOTEBOOK_STORAGE="org.apache.zeppelin.notebook.repo.VFSNotebookRepo,org.apache.zeppelin.notebook.repo.DummyNotebookRepo"
```
2. Start Zeppelin
3. Previously Zeppelin would fail to start, now you would see that only
first storage class is initialized and second just didn't initialize.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/khalidhuseynov/incubator-zeppelin
storage-init-failure-recovery
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/582.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 #582
----
commit d4dc62f85ebec0421dbd5763258de368e49882f5
Author: Khalid Huseynov <[email protected]>
Date: 2015-12-29T10:31:13Z
remove throwing exception, handle gracefully
commit 8f766320aea2bad14d5aa9c8df97607213a4733c
Author: Khalid Huseynov <[email protected]>
Date: 2015-12-29T10:31:52Z
add tests for different configs
----
---
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.
---
