You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/07/29 02:53:04 UTC

[jira] [Resolved] (SPARK-9421) Fix null-handling bug in UnsafeRow.getDouble, getFloat(), and get(ordinal, dataType)

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

Josh Rosen resolved SPARK-9421.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

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

> Fix null-handling bug in UnsafeRow.getDouble, getFloat(), and get(ordinal, dataType)
> ------------------------------------------------------------------------------------
>
>                 Key: SPARK-9421
>                 URL: https://issues.apache.org/jira/browse/SPARK-9421
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.5.0
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>             Fix For: 1.5.0
>
>
> UnsafeRow.getDouble and getFloat() return NaN when called on columns that are null, which is inconsistent with the behavior of other row classes (which is to return 0.0).
> In addition, the generic get(ordinal, dataType) method should always return {{null}} for a null literal, but currently it returns the same thing as the more specific getters.



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