GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2455
ZEPPELIN-1515. Notebook: HDFS as a backend storage (Read & Write Mode)
### What is this PR for?
This PR is trying to add hdfs as another implementation for `NotebookRepo`.
There's another PR about using webhdfs to implement that. Actually hdfs client
library is compatibility cross major versions. See
http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html#Wire_compatibility
This PR is also required for HA of zeppelin, so that multiple zeppelin
instances can share notes via hdfs. Besides I add hadoop-client in pom file.
So zeppelin will package hadoop client jar into its binary distribution. This
is because zeppelin may be installed in a gateway machine where no hadoop is
installed (only hadoop configuration file is existed in this machine)
### What type of PR is it?
[Feature]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1515
### How should this be tested?
Unit test is added. Also manually verify it in a single node cluster.
### 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/zjffdu/zeppelin ZEPPELIN-1515
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2455.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 #2455
----
commit 2857369734d8eb698cde2286c49fdccfd6ed2eea
Author: Jeff Zhang <[email protected]>
Date: 2017-06-30T06:48:22Z
ZEPPELIN-1515. Notebook: HDFS as a backend storage (Read & Write Mode)
----
---
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.
---
