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 2017/06/14 01:54:00 UTC

[jira] [Created] (SPARK-21086) CrossValidator, TrainValidationSplit should preserve all models after fitting

Joseph K. Bradley created SPARK-21086:
-----------------------------------------

             Summary: CrossValidator, TrainValidationSplit should preserve all models after fitting
                 Key: SPARK-21086
                 URL: https://issues.apache.org/jira/browse/SPARK-21086
             Project: Spark
          Issue Type: New Feature
          Components: ML
    Affects Versions: 2.2.0
            Reporter: Joseph K. Bradley


I've heard multiple requests for having CrossValidatorModel and TrainValidationSplitModel preserve the full list of fitted models.  This sounds very valuable.

One decision should be made before we do this: Should we save and load the models in ML persistence?  That could blow up the size of a saved Pipeline if the models are large.
* I suggest *not* saving the models by default but allowing saving if specified.  We could specify whether to save the model as an extra Param for CrossValidatorModelWriter, but we would have to make sure to expose CrossValidatorModelWriter as a public API and modify the return type of CrossValidatorModel.write to be CrossValidatorModelWriter (but this will not be a breaking change).



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