GitHub user fireboy1919 reopened a pull request:

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

    Pool pluggable rebase

    ### 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 saved to disk so that they can be reloaded.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    * [X] - Add ability to use different kinds of resource pools, and show a 
second type.
    
    ### What is the Jira issue?
    Partially implements this:  
https://issues.apache.org/jira/browse/ZEPPELIN-699
    
    Note, that this pull request is dependent upon this one:  
    https://github.com/apache/incubator-zeppelin/pull/782
    
    ### 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
    
    ### 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 
pool_pluggable_rebase

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

    https://github.com/apache/incubator-zeppelin/pull/843.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 #843
    
----

----


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