Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11266#issuecomment-191680086
@yinxusen I notice that your change made ```Pipeline``` and
```PipelineModel``` as the wrapper of peer Java object. But I vote to keep the
exist behavior, ```Pipeline``` still should be a pure Python object.
We do not need to bother a peer Java object for ```Pipeline```. Because
most stages(Estimator/Transformer) have already supported save/load, so
implementing ```Pipeline``` persistence at Python side is more simple than your
change.
May be we should here others' thoughts. cc @mengxr @jkbradley
---
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]
