GitHub user zjffdu reopened a pull request:

    https://github.com/apache/zeppelin/pull/1751

    ZEPPELIN-1786. Refactor LivyHelper

    ### What is this PR for?
    
    This PR continue the work of livy refactoring. Here's the main changes in 
this PR
    * Move the code from `LivyHelper` to `BaseLivyInterprereter`
    * Define POJO for livy request and response
    * Move the livy session initialization from `interpret` to `open`
    * Add one more complicated test which use the spark basic tutorial note.
    * Support livy.sql for spark2
    * Use zeppelin.livy.create.session.timeout instead of retry count as retry 
count is internal implementation and user don't know what does it mean.
    * Improve travis (wrap livy related work in `setupLivy.sh`) 
    
    
    ### What type of PR is it?
    [Improvement | Refactoring]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1786
    
    ### How should this be tested?
    
    One more integration test is added
    
    ### 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-1786

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1751.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 #1751
    
----
commit 0a1aa5dd993141efb6034b4799ba8aebec1a80dc
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-12-12T04:02:03Z

    ZEPPELIN-1786. Refactor LivyHelper

----


---
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.
---

Reply via email to