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 2016/03/21 03:52:33 UTC

[jira] [Closed] (SPARK-7461) Remove spark.ml Model, and have all Transformers have parent

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

Joseph K. Bradley closed SPARK-7461.
------------------------------------
    Resolution: Won't Fix

> Remove spark.ml Model, and have all Transformers have parent
> ------------------------------------------------------------
>
>                 Key: SPARK-7461
>                 URL: https://issues.apache.org/jira/browse/SPARK-7461
>             Project: Spark
>          Issue Type: Sub-task
>          Components: ML
>            Reporter: Joseph K. Bradley
>
> A recent PR [https://github.com/apache/spark/pull/5980] brought up an issue with the Model abstraction: There are transformers which could be Transformers (created by a user) or Models (created by an Estimator).  This is the first instance, but there will be more such transformers in the future.
> Some possible fixes are:
> * Create 2 separate classes, 1 extending Transformer and 1 extending Model.  These would be essentially the same, and they could share code (or have 1 wrap the other).  This would bloat the API.
> * Just use Model, with a possibly null parent class.  There is precedence (meta-algorithms like RandomForest producing weak hypothesis Models with no parent).
> * Change Transformer to have a parent which may be null.
> ** *--> Unless there is strong disagreement, I think we should go with this last option.*



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