[jira] [Commented] (PARQUET-1251) Clarify ambiguous min/max stats for FLOAT/DOUBLE

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on PARQUET-1251:
-----------------------------------------

gszadovszky opened a new pull request #88: PARQUET-1251: Clarify ambiguous min/max stats for FLOAT/DOUBLE
URL: https://github.com/apache/parquet-format/pull/88
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Clarify ambiguous min/max stats for FLOAT/DOUBLE
> ------------------------------------------------
>
>                 Key: PARQUET-1251
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1251
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-format
>    Affects Versions: format-2.4.0
>            Reporter: Gabor Szadovszky
>            Assignee: Gabor Szadovszky
>            Priority: Major
>
> Describe the handling of the ambigous min/max statistics for FLOAT/DOUBLE types in case of TypeDefinedOrder. (See PARQUET-1222 for details.)
> * When looking for NaN values, min and max should be ignored.
> * If the min is a NaN, it should be ignored.
> * If the max is a NaN, it should be ignored.
> * If the min is +0, the row group may contain -0 values as well.
> * If the max is -0, the row group may contain +0 values as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)