GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/1462
ZEPPELIN-1477. Add Integration Test for LivyInterpreter
### What is this PR for?
This PR fix several issues of LivyInterpeter test.
* Livy interpreter's test code is not in the right place, so it never runs.
* LivyHelperTest would fail.
* No Integration test for LivyInterpreter so any following change is not
easy to be tested.
This PR would fix the above issues. Regarding the integration test, some of
livy's artifact is not available in repository, so I have to copy them to
livy/local-maven-repo as local repository. And LivyInterperter's integration
test require spark and livy to be installed. For now you have to download spark
and livy manually. Please use spark 1.5.x and livy 0.2. Download livy 0.2.0
from here https://github.com/cloudera/livy/releases
And use the following command to execute the LivyIntegrationTest.
```
export SPARK_HOME=<>
export LIVY_HOME=<>
mvn clean package -pl 'livy' -Dtest=LivyIntegrationTest
```
If you hit any issues, you can check logs under `livy/target/tmp`.
### What type of PR is it?
[Bug Fix | Improvement]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1477
### 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-1477
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1462.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 #1462
----
commit 152d346bb89f9b2de1c0f844ca53c93d8e9301ee
Author: Jeff Zhang <zjf...@apache.org>
Date: 2016-09-22T08:42:14Z
ZEPPELIN-1477. Add Integration Test for LivyInterpreter
----
---
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.
---
