GitHub user kavinkumarks opened a pull request:

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

    [ZEPPELIN-1268]

    ### What is this PR for?
    This pull request is to add the below options so when someone develops a 
custom UI it would ease them.
    1. Add a new option "Get paragraph id" in the notebook UI
    2. Add a new REST API to get the status of a single paragraph
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * Need to update the REST APIs documentation 
http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/rest-api/rest-notebook.html#get-the-status-of-all-paragraphs
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-1268
    
    ### How should this be tested?
    * Navigate to the notebook UI and a new option "Get paragraph id" will be 
shown for each paragraph and on clicking on it, the paragraph id would be 
alerted
    * The new REST API 
http://%5Bzeppelin-server%5D:%5Bzeppelin-port%5D/api/notebook/job/%5BnotebookId%5D/%5BparagraphId%5D
 could be accessed to get the status of a single paragraph.
    
    ### Screenshots (if appropriate)
    
    ### Questions:

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kavinkumarks/zeppelin zeppelin-1268-custom-UI

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

    https://github.com/apache/zeppelin/pull/1262.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 #1262
    
----
commit a449992256d8badf72a412ccc0e3134873d5db31
Author: Kavin <kavin.ku...@imaginea.com>
Date:   2016-08-02T11:07:35Z

    Changes to show new option to get paragraph id in notebook UI and new REST 
API to get status of a single paragraph

----


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