GitHub user fireboy1919 opened a pull request:

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

    Resource pools api

    ### What is this PR for?
    This is a step towards creating a REST endpoint from resource pools  
https://issues.apache.org/jira/browse/ZEPPELIN-699
    
    It allows resources to be downloaded from results using a REST API
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * [X] - Add ability to download resources via an API endpoint
    
    ### What is the Jira issue?
    Finishes:  https://issues.apache.org/jira/browse/ZEPPELIN-699
    
    Note, that this pull request is based upon these:  
    https://github.com/apache/incubator-zeppelin/pull/782
    https://github.com/apache/incubator-zeppelin/pull/816
    
    ### How should this be tested?
    1.  Edit an interpreter
    2.  Add a new property to the interpreter - the "ResourcePoolClass" - and 
assign it to "org.apache.zeppelin.resource.VFSResourcePool" 
    3.  Run the interpreter
    
    You should see new resource files created in notebook/zeppelin_resources
    
    Then go to 
    `/api/notebook/results`
    to see the rest endpoint that lists all of the results.
    
    View it with
    `/api/notebook/[noteid]/paragraph/[paragraph id]/results`
    
    ### 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/fireboy1919/incubator-zeppelin 
resource_pools_api

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

    https://github.com/apache/incubator-zeppelin/pull/822.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 #822
    
----
commit cbdb22d309948eaa2d7562c66c3b8780a6581647
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-15T23:11:20Z

    Added serialization to resourcepoolutils.

commit ffd092b6e7df495ecd1f4e753e3e88678bae2ead
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-15T23:06:35Z

    Added pool persistance.

commit 84cabe2d02a7cf49a82f56d8ae8cbbecb6699aaf
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-16T14:59:29Z

    Added test.

commit ffce0d9cfdd81fb7e27928f621c3cd58a02cb5d9
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-17T18:45:55Z

    Fixed merge conflict.

commit 187e45e9c26462b53cdd942316f09c614421b7ca
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-17T18:46:22Z

    Merge remote-tracking branch 'apache/master' into persist_pool

commit f1f0d91dbce47a50d5f9737b052ee1f73cc04590
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-28T16:14:36Z

    Changed resource pool utils so that it will work anywhere.

commit a19c48e124cf45b6287656133bd4dca26dcce002
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-28T17:42:00Z

    Removed unnecessary serialization.

commit 8fa84a832200351465793f83aafe8d1c0c3c3573
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-28T21:02:18Z

    Added explicit save to the serializer.

commit 1f2d2ec3306fa0b6dd2ffe907b7e5566cd0fc391
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-03-21T19:46:03Z

    Added vfs resource pool.

commit 5ab296206c79136a06267b90e5d0758de3eacb95
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-04-05T20:37:40Z

    Added pluggable resource pool.

commit 47e0ee5978d897234173711cf54b119eb32d0140
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-04-06T13:00:53Z

    Added missing rename.

commit 3c0e0c2736bf91a2f99b38a3c343046e676e0e75
Author: Rusty Phillips <ru...@cloudspace.com>
Date:   2016-04-06T14:44:43Z

    Added an API to access resource pools.

----


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