You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2016/04/29 20:27:12 UTC
[jira] [Commented] (SPARK-13786) Pyspark ml.tuning support
export/import
[ https://issues.apache.org/jira/browse/SPARK-13786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264482#comment-15264482 ]
Joseph K. Bradley commented on SPARK-13786:
-------------------------------------------
Per discussion on [https://github.com/apache/spark/pull/12604], I'm going to remove PySpark tuning export/import. I'll do it in a new PR (rather than reverting a commit) because of significant merge conflicts.
> Pyspark ml.tuning support export/import
> ---------------------------------------
>
> Key: SPARK-13786
> URL: https://issues.apache.org/jira/browse/SPARK-13786
> Project: Spark
> Issue Type: Sub-task
> Components: ML, PySpark
> Reporter: Joseph K. Bradley
> Assignee: Xusen Yin
> Fix For: 2.0.0
>
>
> This should follow whatever implementation is chosen for Pipeline (since these are all meta-algorithms).
> Note this will also require persistence for Evaluators. Hopefully that can leverage the Java implementations; there is not a real need to make Python Evaluators be MLWritable, as far as I can tell.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org