You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2018/03/20 15:21:00 UTC
[jira] [Updated] (PARQUET-1251) Clarify ambiguous min/max stats for
FLOAT/DOUBLE
[ https://issues.apache.org/jira/browse/PARQUET-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Szadovszky updated PARQUET-1251:
--------------------------------------
Summary: Clarify ambiguous min/max stats for FLOAT/DOUBLE (was: Describe handling of the ambigous min/max statistics for FLOAT/DOUBLE)
> 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)