[
https://issues.apache.org/jira/browse/SPARK-15614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306419#comment-15306419
]
zhengruifeng commented on SPARK-15614:
--------------------------------------
Agreed.
What about setting the default value of {{setInputCol}} if the algorithm takes
features as input?
> ml.feature should support default value of input column
> -------------------------------------------------------
>
> Key: SPARK-15614
> URL: https://issues.apache.org/jira/browse/SPARK-15614
> Project: Spark
> Issue Type: Brainstorming
> Components: ML
> Reporter: zhengruifeng
> Priority: Minor
>
> {{ml.clasification}} and {{ml.clustering}} use {{"features"}} as default
> input column. While {{ml.feature}} use {{setInputCol}} method to set input
> column and don't have default value, which is somewhat strange.
> It may be nice to support default input column "features" in {{ml.feature}},
> and we can make these implements extends {{HasFeaturesCol}} and make existing
> {{setInputCol}} method just a alias.
> I can work on this if needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
