[GitHub] zeppelin pull request #1161: [ZEPPELIN-906] Apply new mechanism to AlluxioIn...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1161 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1161: [ZEPPELIN-906] Apply new mechanism to AlluxioIn...
Github user AhyoungRyu closed the pull request at: https://github.com/apache/zeppelin/pull/1161 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1161: [ZEPPELIN-906] Apply new mechanism to AlluxioIn...
GitHub user AhyoungRyu reopened a pull request: https://github.com/apache/zeppelin/pull/1161 [ZEPPELIN-906] Apply new mechanism to AlluxioInterpreter ### What is this PR for? This PR applies the [new interpreter registration mechanism](https://issues.apache.org/jira/browse/ZEPPELIN-804) to Alluxio interpreter. ### What type of PR is it? Improvement ### Todos * [x] - Remove static property definition code lines in `AlluxioInterpreter.java` and create `interpreter-setting.json` under `alluxio/src/main/resources` dir ### What is the Jira issue? [ZEPPELIN-906](https://issues.apache.org/jira/browse/ZEPPELIN-906) ### How should this be tested? 1. apply this patch 2. rm -r `interpreter/alluxio` and rm `conf/interpreter.json` 3. build source 4. bin/zeppelin-daemon.sh start 5. Run a paragraph with alluxio commands ### 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/AhyoungRyu/zeppelin ZEPPELIN-906 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1161.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 #1161 commit b86ae3fc338eba6adb8e5bb37f0a9c691132dc12 Author: AhyoungRyu Date: 2016-07-11T03:39:30Z Apply new mechanism to AlluxioInterpreter commit 7a332cc2fb2d72247f85e9e812794285eec1ecbf Author: AhyoungRyu Date: 2016-07-11T09:39:07Z Fix typo --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1161: [ZEPPELIN-906] Apply new mechanism to AlluxioIn...
GitHub user AhyoungRyu opened a pull request: https://github.com/apache/zeppelin/pull/1161 [ZEPPELIN-906] Apply new mechanism to AlluxioInterpreter ### What is this PR for? This PR applies the [new interpreter registration mechanism](https://issues.apache.org/jira/browse/ZEPPELIN-804) to Alluxio interpreter. ### What type of PR is it? Improvement ### Todos * [x] - Remove static property definition code lines in `AlluxioInterpreter.java` and create `interpreter-setting.json` under `alluxio/src/main/resources` dir ### What is the Jira issue? [ZEPPELIN-906](https://issues.apache.org/jira/browse/ZEPPELIN-906) ### How should this be tested? 1. apply this patch 2. rm -r `interpreter/alluxio` and rm `conf/interpreter.json` 3. build source 4. bin/zeppelin-daemon.sh start 5. Run a paragraph with alluxio commands ### 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/AhyoungRyu/zeppelin ZEPPELIN-906 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1161.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 #1161 commit b86ae3fc338eba6adb8e5bb37f0a9c691132dc12 Author: AhyoungRyu Date: 2016-07-11T03:39:30Z Apply new mechanism to AlluxioInterpreter --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
