GitHub user zjffdu reopened a pull request:

    ZEPPELIN-1607. Refactor Livy Interpreter to adapt scope mode

    ### What is this PR for?
    ZEPPELIN-1606 will make scoped mode as the default interpreter mode of 
livy. This PR is to refactor livy interpreter to adapt the scoped mode. 
Besides, it also fix several bugs of livy interpreter.  like ZEPPELIN-1516. 
Besides that I also enable livy integration test in travis to make sure the 
refactoring correct. 
    ### What type of PR is it?
    ### Todos
    * Move session creation to open()
    * Other refactoring in livy interpreter, especially
    ### What is the Jira issue?
    ### How should this be tested?
    Travis is also enabled for livy integration test. 
    ### 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 ZEPPELIN-1607

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1612
commit cbc7689442860956c0951e1703ddc8bafb22fb0f
Author: Jeff Zhang <>
Date:   2016-11-03T06:21:33Z

    ZEPPELIN-1607. Refactor Livy Interpreter to adapt scope mode

commit 132783ddfbc9034e95c823610e97f66c04b01ab7
Author: Jeff Zhang <>
Date:   2016-11-08T08:29:17Z

    enable travis for livy integration test

commit c539cde6d0d16cd7ce82f0a39e1db22391db1603
Author: Jeff Zhang <>
Date:   2016-11-08T09:11:10Z

    add licence header

commit ad2329228c58fc30665ba0bdab6cae350b96c590
Author: Jeff Zhang <>
Date:   2016-11-08T09:12:25Z

    update .travis.yml

commit 14ef0690224dd2e64dc52c56e3b29a88632f1ad4
Author: Jeff Zhang <>
Date:   2016-11-08T09:44:30Z

    update test

commit e3cec8b04bcbb96cc1bd14a0f5718ee9be79eb19
Author: Jeff Zhang <>
Date:   2016-11-29T00:12:31Z

    change version from 2.3 to 2.6 in .travis.yml


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 or file a JIRA ticket
with INFRA.

Reply via email to