You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/04/25 00:24:39 UTC
[jira] [Resolved] (SPARK-1457) Change APIs for training algorithms
to take optimizer as parameter
[ https://issues.apache.org/jira/browse/SPARK-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-1457.
------------------------------
Resolution: Won't Fix
I think this is not a bad idea but think this might have timed out, and will be superseded by the new ML API anyway.
> Change APIs for training algorithms to take optimizer as parameter
> -------------------------------------------------------------------
>
> Key: SPARK-1457
> URL: https://issues.apache.org/jira/browse/SPARK-1457
> Project: Spark
> Issue Type: Improvement
> Components: MLlib
> Reporter: DB Tsai
> Priority: Minor
>
> Currently, the training api has signature like LogisticRegressionWithSGD.
> If we want to use another optimizer, we've two options, either adding new api like LogisticRegressionWithNewOptimizer which causes 99% of the code duplication, or we can re-factorize the api to take the optimizer as an option like the following.
> class LogisticRegression private (
> var optimizer: Optimizer)
> extends GeneralizedLinearAlgorithm[LogisticRegressionModel]
--
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