GitHub user apc999 opened a pull request:
https://github.com/apache/zeppelin/pull/2900
Alluxio
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://zeppelin.apache.org/contribution/contributions.html
### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
### Todos
* [ ] - Task
### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg.
[ZEPPELIN-533]
### How should this be tested?
* First time? Setup Travis CI as described on
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
* Strongly recommended: add automated unit tests for any new or changed
behavior
* Outline any manual steps to test the PR here.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apc999/zeppelin alluxio
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2900.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 #2900
----
commit 2b479435ced0d3ea1c9bdfb0695e63f9fcdca544
Author: Bin Fan <fanbin103@...>
Date: 2018-03-28T00:22:02Z
Bump alluxio depenedency version to 1.7.0 and make it compile
commit 1631c9479eca8da48e1f35a7882f408b7adb04e2
Author: Bin Fan <fanbin103@...>
Date: 2018-03-29T23:21:11Z
Ignore tests because Alluxio MiniCluster breaks when used as library
----
---
