You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Ajay Saini (JIRA)" <ji...@apache.org> on 2017/06/27 01:12:00 UTC

[jira] [Issue Comment Deleted] (SPARK-21221) CrossValidator and TrainValidationSplit Persist Nested Estimators

     [ https://issues.apache.org/jira/browse/SPARK-21221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ajay Saini updated SPARK-21221:
-------------------------------
    Comment: was deleted

(was: Pull Request Here: https://github.com/apache/spark/pull/18428)

> CrossValidator and TrainValidationSplit Persist Nested Estimators
> -----------------------------------------------------------------
>
>                 Key: SPARK-21221
>                 URL: https://issues.apache.org/jira/browse/SPARK-21221
>             Project: Spark
>          Issue Type: New Feature
>          Components: ML
>    Affects Versions: 2.1.1
>            Reporter: Ajay Saini
>
> Currently, the saving of parameters done in ValidatorParams.scala assumes that all parameters in EstimatorParameterMaps are JSON serializable. Such an assumption causes CrossValidator and TrainValidationSplit persistence to fail when the internal estimator to these meta-algorithms is not JSON serializable. One example is OneVsRest which has a classifier (estimator) as a parameter.
> The changes would involve removing the assumption in validator params that all the estimator params are JSON serializable. This could mean saving parameters that are not JSON serializable separately at a specified path. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org