GitHub user zjffdu opened a pull request:

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

    ZEPPELIN-2015 Improve parsing logic of livy sql output

    ### What is this PR for?
    This PR is trying to resolve the table display issue related with #1942. 
But when I do this PR, I find other 2 issues in livy interpreter.
    * livy integration is never run due to refactoring of travis script in 
#1786.
    * pyspark integration would fail
    
    
    ### What type of PR is it?
    [Bug Fix | Improvement]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2015
    
    
    ### 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-2015

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

    https://github.com/apache/zeppelin/pull/1950.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 #1950
    
----
commit ba6aab2c391ca72ca97e1ccfa79dc368b1ad96d2
Author: Chin Tzulin <[email protected]>
Date:   2017-01-25T05:34:28Z

    [ZEPPELIN-1982] When using the 'Select * ...' statement doesn't show the 
response In %sql interpreter

commit 4667eef79ecb16b93d2a187dfdf3b4004dc5a77c
Author: Jeff Zhang <[email protected]>
Date:   2017-01-26T09:30:49Z

    ZEPPELIN-2015. Improve parsing logic of livy sql output

commit 98b1d96e4e031d438268834840ab2761e5012c6a
Author: Jeff Zhang <[email protected]>
Date:   2017-01-26T14:47:56Z

    Fix appId and webui extraction for pyspark

----


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

Reply via email to