GitHub user zjffdu opened a pull request:

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

    [WIP] ZEPPELIN-1852. Use multiple InterpreterResult for displaying appInfo

    ### What is this PR for?
    Refactor the livy interpreter to use multiple `InterpreterResult` for 
displaying appInfo. 
    
    
    ### What type of PR is it?
    [Refactoring]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1852
    
    ### How should this be tested?
    Add integration test and also test it manually
    
    ### Screenshots (if appropriate)
    
![image](https://cloud.githubusercontent.com/assets/164491/21446563/9e3c9e78-c902-11e6-8bf6-84788d1dfb51.png)
    
    ### 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-1852

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

    https://github.com/apache/zeppelin/pull/1796.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 #1796
    
----
commit e800932d9070e9c82b96802592ae4a6a0cfe0000
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-12-23T03:14:32Z

    ZEPPELIN-1851. LazyOpenInterpreter would open interpreter multiple times 
when open fails

commit e34e4f52d3510fc2a6233a580f7d21cda6a98476
Author: Jeff Zhang <zjf...@apache.org>
Date:   2016-12-23T03:24:27Z

    ZEPPELIN-1852. Use multiple InterpreterResult for displaying appInfo

----


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