wgtmac commented on PR #3393: URL: https://github.com/apache/parquet-java/pull/3393#issuecomment-5112319292
> A legacy reader that recognizes type_order but not nan_count may use the min/max values without realizing that NaNs are present. I don't think so. NaNs are not written to the min/max for `type_order`, otherwise it is a bug. Could you double check? BTW, legacy readers cannot assume `min/max statistics are omitted whenever NaNs exist`. They are just educated to regard stats with NaN values as invalid. > With a new column order, there's chance that reader checks the column order, and drop the stats for UNKNOWN column order. This is exactly the concern that I have. Readers may have just hard-coded `type-order` without notice of a new column order. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
