[jira] [Commented] (SPARK-5256) Improving MLlib optimization APIs

["Joseph K. Bradley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486184#comment-14486184 ] 

Joseph K. Bradley commented on SPARK-5256:
------------------------------------------

(Comment related to link to [SPARK-6682]) Builder methods for GLMs have issues because of the Optimizer API.  (See discussion above: The constructors for Optimizer require Gradient and Updater.)  Cleaning up the Optimizer API will facilitate moving to the builder API.

> Improving MLlib optimization APIs
> ---------------------------------
>
>                 Key: SPARK-5256
>                 URL: https://issues.apache.org/jira/browse/SPARK-5256
>             Project: Spark
>          Issue Type: Umbrella
>          Components: MLlib
>    Affects Versions: 1.2.0
>            Reporter: Joseph K. Bradley
>
> *Goal*: Improve APIs for optimization
> *Motivation*: There have been several disjoint mentions of improving the optimization APIs to make them more pluggable, extensible, etc.  This JIRA is a place to discuss what API changes are necessary for the long term, and to provide links to other relevant JIRAs.
> Eventually, I hope this leads to a design doc outlining:
> * current issues
> * requirements such as supporting many types of objective functions, optimization algorithms, and parameters to those algorithms
> * ideal API
> * breakdown of smaller JIRAs needed to achieve that API
> I will soon create an initial design doc, and I will try to watch this JIRA and include ideas from JIRA comments.



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