GitHub user zjffdu opened a pull request:
https://github.com/apache/zeppelin/pull/2422
[WIP] [ZEPPELIN-2627] Interpreter refactor
### 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 interpreter_refactor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2422.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 #2422
----
commit 8ee3f45dffa7feff4b95f0ac0cdf6ac3fc69f61b
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-05-23T07:52:15Z
save
commit 2ca2188cd157ec509b5b982ffeaaae2d3f954d07
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-06-18T05:52:26Z
fix Job race
----
---
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.
---
