You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2021/09/27 03:15:00 UTC

[jira] [Resolved] (SPARK-36838) Improve InSet NaN check generated code performance

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

Hyukjin Kwon resolved SPARK-36838.
----------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

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

> Improve InSet NaN check generated code performance
> --------------------------------------------------
>
>                 Key: SPARK-36838
>                 URL: https://issues.apache.org/jira/browse/SPARK-36838
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.0.3, 3.1.2, 3.2.0
>            Reporter: angerszhu
>            Assignee: Apache Spark
>            Priority: Minor
>             Fix For: 3.3.0
>
>
> Since Set can't check is NaN value is contained in current set.
> With codegen, only when value set contains NaN then we have necessary to check if the value is NaN, or we just need t
> o check is the Set contains the value.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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