GitHub user zjffdu reopened a pull request:
https://github.com/apache/zeppelin/pull/2010
[WIP] ZEPPELIN-2079. Upgrade livy to 0.3 in livy interpreter
### 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?
Outline the 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/zjffdu/zeppelin ZEPPELIN-2079
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2010.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 #2010
----
commit 2695d7c7fe02864c9918bfa81f80af3651d2775c
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-02-08T07:59:07Z
ZEPPELIN-2079. Upgrade livy to 0.3 in livy interpreter
commit e9d10421256174558dc07de0c6723a0dba6709ff
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-02-13T01:06:39Z
update travis
----
---
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.
---
