You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Nicholas Chammas (Jira)" <ji...@apache.org> on 2024/02/06 15:34:00 UTC

[jira] [Commented] (SPARK-26575) revisit the equality of NaN

    [ https://issues.apache.org/jira/browse/SPARK-26575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814867#comment-17814867 ] 

Nicholas Chammas commented on SPARK-26575:
------------------------------------------

And just for others who happen to come across this issue, Spark's current [NaN semantics are documented nicely here|https://github.com/apache/spark/blob/cd19d6c299a7bc6d8a785208654dff132ca5fe1b/docs/sql-ref-datatypes.md?plain=1#L285-L294].

> revisit the equality of NaN
> ---------------------------
>
>                 Key: SPARK-26575
>                 URL: https://issues.apache.org/jira/browse/SPARK-26575
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Wenchen Fan
>            Priority: Major
>
> In Spark SQL, we treat all the NaN values as same. This is against IEEE floating point
> standard. We should revisit it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org