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

Yanbo Liang resolved SPARK-17141.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

> MinMaxScaler behaves weird when min and max have the same value and some 
> values are NaN
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-17141
>                 URL: https://issues.apache.org/jira/browse/SPARK-17141
>             Project: Spark
>          Issue Type: Bug
>          Components: ML
>    Affects Versions: 1.6.2, 2.0.0
>         Environment: Databrick's Community, Spark 2.0 + Scala 2.10
>            Reporter: Alberto Bonsanto
>            Assignee: Yanbo Liang
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> When you have a {{DataFrame}} with a column named {{features}}, which is a 
> {{DenseVector}} and the *maximum* and *minimum* and some values are 
> {{Double.NaN}} they get replaced by 0.5, and they should remain with the same 
> value, I believe.
> I know how to fix it, but I haven't ever made a pull request. You can check 
> the bug in this 
> [notebook|https://databricks-prod-cloudfront.cloud.databricks.com/public/4027ec902e239c93eaaa8714f173bcfc/2485090270202665/3126465289264547/8589256059752547/latest.html]



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

Reply via email to