[GitHub] zeppelin pull request #2900: Alluxio
GitHub user apc999 reopened a pull request: https://github.com/apache/zeppelin/pull/2900 Alluxio ### What is this PR for? Zeppelin provides an Alluxio interpreter compiled with Alluxio client v1.0.0, which was released about two years ago. Alluxio 1.0.0 client will not work with Alluxio 1.4 or later. So in order to use Zeppelin with latest Alluxio, we need to increment the version. This JIRA aims to bump the version of Alluxio from 1.0.0 to 1.7.1 (the latest release in March 2018) ### What type of PR is it? [Improvement] ### What is the Jira issue? [ZEPPELIN-3373](https://issues.apache.org/jira/browse/ZEPPELIN-3373) ### How should this be tested? Manual test: - Build Zeppelin with this patch - Launch Zeppelin Alluxio interpreter and test the interpreter. ### Screenshots (if appropriate) [Screenshot](https://issues.apache.org/jira/secure/attachment/12916912/Screen%20Shot%202018-03-27%20at%205.32.36%20PM.png) ### Questions: * Does the licenses files need update? n/a * Is there breaking changes for older versions? n/a * Does this needs documentation? [docs](https://zeppelin.apache.org/docs/latest/interpreter/alluxio.html) needs to be updated 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 FanDate: 2018-03-28T00:22:02Z Bump alluxio depenedency version to 1.7.0 and make it compile commit 1631c9479eca8da48e1f35a7882f408b7adb04e2 Author: Bin Fan Date: 2018-03-29T23:21:11Z Ignore tests because Alluxio MiniCluster breaks when used as library ---
[GitHub] zeppelin pull request #2900: Alluxio
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 FanDate: 2018-03-28T00:22:02Z Bump alluxio depenedency version to 1.7.0 and make it compile commit 1631c9479eca8da48e1f35a7882f408b7adb04e2 Author: Bin Fan Date: 2018-03-29T23:21:11Z Ignore tests because Alluxio MiniCluster breaks when used as library ---