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

Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/04/09 11:25:16 UTC

[jira] [Resolved] (SPARK-1300) Clean-up and clarify private vs public fields in MLLib

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

Patrick Wendell resolved SPARK-1300.
------------------------------------

    Resolution: Fixed

> Clean-up and clarify private vs public fields in MLLib
> ------------------------------------------------------
>
>                 Key: SPARK-1300
>                 URL: https://issues.apache.org/jira/browse/SPARK-1300
>             Project: Spark
>          Issue Type: Improvement
>          Components: MLlib
>            Reporter: Patrick Wendell
>            Assignee: Xiangrui Meng
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> Some of the MLLib implementations have random internal varaibles that are exposed and should be made private.
> For the regression package, there are a few fields (optimizer, updater, gradient) that we should just make private[spark].
> For other internal components we should annotate them as semi-private. I.e. they are deeper API's for more advanced developers.



--
This message was sent by Atlassian JIRA
(v6.2#6252)