GitHub user prabhjyotsingh opened a pull request:

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

    ZEPPELIN-850 update error message

    ### What is this PR for?
    If there is an error on a paragraph, and user tries to run that paragraph 
again, which results in a different error message. In this case paragraph does 
not show up new error message.
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### What is the Jira issue?
    * [ZEPPELIN-850](https://issues.apache.org/jira/browse/ZEPPELIN-850)
    
    ### How should this be tested?
     - create a new notebook
     - on the try running paragraph by using a wrong value for interpreter like 
%spark.error
     - on try changing the same with say %spark.error2
    observe the paragraph output it should changed.
    
    ### Screenshots (if appropriate)
    Before:
    
![error](https://cloud.githubusercontent.com/assets/674497/15212273/6afae5b6-185d-11e6-815e-2de8b0f9364b.gif)
    
    After:
    
![fixed](https://cloud.githubusercontent.com/assets/674497/15212274/6b012822-185d-11e6-98e1-44cb86951595.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/prabhjyotsingh/incubator-zeppelin ZEPPELIN-850

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

    https://github.com/apache/incubator-zeppelin/pull/888.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 #888
    
----
commit 58e7ddcfee886bfa057b02f770bdf7617458df5d
Author: Prabhjyot Singh <prabhjyotsi...@gmail.com>
Date:   2016-05-12T10:46:23Z

    ZEPPELIN-850 update error message

----


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