You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:15:19 UTC
[jira] [Resolved] (SPARK-5844) Optimize Pipeline.fit for ParamGrid
[ https://issues.apache.org/jira/browse/SPARK-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-5844.
---------------------------------
Resolution: Incomplete
> Optimize Pipeline.fit for ParamGrid
> -----------------------------------
>
> Key: SPARK-5844
> URL: https://issues.apache.org/jira/browse/SPARK-5844
> Project: Spark
> Issue Type: Improvement
> Components: ML
> Affects Versions: 1.3.0
> Reporter: Joseph K. Bradley
> Priority: Major
> Labels: bulk-closed
>
> This issue was brought up by [~prudenko] in [this JIRA | https://issues.apache.org/jira/browse/SPARK-4766].
> **Proposal**:
> When Pipeline.fit is given an array of ParamMaps, it should operate incrementally:
> * For each set of parameters applicable to the first PipelineStage,
> ** Fit/transform that stage using that set of parameters.
> ** For each set of parameters applicable to the second PipelineStage,
> *** etc.
> This is essentially a depth-first search on the parameters, where each node/level in the search tree is a PipelineStage and each node's child nodes correspond to the set of ParamMaps for that PipelineStage.
> This will avoid recomputing intermediate RDDs during model search.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org