GitHub user jkbradley opened a pull request:

    https://github.com/apache/spark/pull/11866

    [SPARK-13951][ML][PYTHON] Nested Pipeline persistence

    ## What changes were proposed in this pull request?
    
    Adds support for saving and loading nested ML Pipelines from Python.  
Pipeline and PipelineModel do not extend JavaWrapper, but they are able to 
utilize the JavaMLWriter, JavaMLReader implementations.
    
    Also:
    * Separates out interfaces from Java wrapper implementations for 
MLWritable, MLReadable, MLWriter, MLReader.
    * Moves methods _stages_java2py, _stages_py2java into Pipeline, 
PipelineModel as _transfer_stage_from_java, _transfer_stage_to_java
    
    ## How was this patch tested?
    
    Added new unit test for nested Pipelines.  Abstracted validity check into a 
helper method for the 2 unit tests.

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

    $ git pull https://github.com/jkbradley/spark nested-pipeline-io

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

    https://github.com/apache/spark/pull/11866.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 #11866
    
----
commit 89d538208a0704c43b3752eaec10f5ca7f06b975
Author: Joseph K. Bradley <[email protected]>
Date:   2016-03-21T20:39:02Z

    Added nested Pipeline persistence

commit 1c070e738236407559c00360eea1012880229076
Author: Joseph K. Bradley <[email protected]>
Date:   2016-03-21T20:48:16Z

    cleanups, and style fixes

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to