You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by zjffdu <gi...@git.apache.org> on 2018/03/14 06:42:28 UTC

[GitHub] zeppelin pull request #2866: ZEPPELIN-3328. Add plotting test for LivyInterp...

GitHub user zjffdu opened a pull request:

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

    ZEPPELIN-3328. Add plotting test for LivyInterpreter

    ### What is this PR for?
    Add plotting for LivyInterpreter (Python & R)
    
    
    ### What type of PR is it?
    [Improvement]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-3328
    
    ### How should this be tested?
    * CI pass
    
    ### 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-3328

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

    https://github.com/apache/zeppelin/pull/2866.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 #2866
    
----
commit 1b2a5e43f3561f94a7cfee147d6c41e81710a5a5
Author: Jeff Zhang <zj...@...>
Date:   2018-03-14T05:27:09Z

    ZEPPELIN-3328. Add plotting test for LivyInterpreter

----


---

[GitHub] zeppelin pull request #2866: ZEPPELIN-3328. Add plotting test for LivyInterp...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---

[GitHub] zeppelin issue #2866: ZEPPELIN-3328. Add plotting test for LivyInterpreter

Posted by felixcheung <gi...@git.apache.org>.
Github user felixcheung commented on the issue:

    https://github.com/apache/zeppelin/pull/2866
  
    hey @zjffdu thanks for making all these improvements, could we make sure there is at least one review before merging?
    @Leemoonsoo 


---