GitHub user cloverhearts opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/581

    ZEPPELIN-544 ] After the restart when setting bug fixes interpreters note 
paragraphs state.

    ### What is this PR for?
    Restful api - call upon the setting / interpreter id type,
    The problem occurs in the status of running Paragraphs.
    
    - Paragraphs status code changes and restart missing
    
    ### What type of PR is it?
    Bug Fix
    
    ### Todos
    
    
    ### Is there a relevant Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-544
    ### How should this be tested?
    Paragraphs running after interpreter config change, save -> click okay on 
restart dialog
    
    ### Screenshots (if appropriate)
    #### before
    
![bug_fix_before](https://cloud.githubusercontent.com/assets/10525473/12031890/e7708f6c-adc6-11e5-929e-369cabddb84f.gif)
    
    #### after
    
![bug_fix_after](https://cloud.githubusercontent.com/assets/10525473/12031892/eacbcf8c-adc6-11e5-9c2c-971db02da00e.gif)
    
    ### 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/cloverhearts/incubator-zeppelin 
bug_fix/interpreter_restart_abort

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

    https://github.com/apache/incubator-zeppelin/pull/581.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 #581
    
----
commit f6fe21606cf9fd93055a36b1fd5d7a23643addd2
Author: CloverHearts <estai...@gmail.com>
Date:   2015-12-29T08:45:26Z

    restful api setting-interpreterid bug fix.

----


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