[
https://issues.apache.org/jira/browse/PARQUET-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420942#comment-16420942
]
ASF GitHub Bot commented on PARQUET-1251:
-----------------------------------------
rdblue commented on issue #88: PARQUET-1251: Clarify ambiguous min/max stats
for FLOAT/DOUBLE
URL: https://github.com/apache/parquet-format/pull/88#issuecomment-377624823
+1
Thanks for working on this @gszadovszky and @zivanfi!
----------------------------------------------------------------
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:
[email protected]
> 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
> Fix For: format-2.5.0
>
>
> 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)
