[jira] [Resolved] (SPARK-15668) ml.feature: update check schema to avoid confusion when user use MLlib.vector as input type

["Nick Pentreath (JIRA)" <ji...@apache.org>]

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

Nick Pentreath resolved SPARK-15668.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request 13411
[https://github.com/apache/spark/pull/13411]

> ml.feature: update check schema to avoid confusion when user use MLlib.vector as input type
> -------------------------------------------------------------------------------------------
>
>                 Key: SPARK-15668
>                 URL: https://issues.apache.org/jira/browse/SPARK-15668
>             Project: Spark
>          Issue Type: Bug
>          Components: ML
>            Reporter: yuhao yang
>            Assignee: yuhao yang
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> As we use ml.vector to replace mllib.vector in ml, users use mllib.vector as input column will get error. Yet some error message is confusing:
> s"Input column ${$(inputCol)} must be a vector column")
> The input column probably is already a vector of mllib. Update to avoid the confusion.



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