You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@orc.apache.org by "Owen O'Malley (Jira)" <ji...@apache.org> on 2020/08/22 00:02:00 UTC

[jira] [Commented] (ORC-370) ORC column statistics should not use java.sql.Date

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

Owen O'Malley commented on ORC-370:
-----------------------------------

This has also come up in the Iceberg use case and needs to be fixed.

> ORC column statistics should not use java.sql.Date
> --------------------------------------------------
>
>                 Key: ORC-370
>                 URL: https://issues.apache.org/jira/browse/ORC-370
>             Project: ORC
>          Issue Type: Bug
>    Affects Versions: 1.4.4, 1.5.1
>            Reporter: Prasanth Jayachandran
>            Assignee: Owen O'Malley
>            Priority: Blocker
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ORC PPD evaluation for Date type uses java.sql.Date for min/max comparison causing incorrect results.
> Date.compareTo uses millis offset which can return incorrect results depending on the timezone. 
> Running the testcase in HIVE-19726 passed in Los Angeles but failed in Paris as Date.compareTo return 0 for Los Angeles but returned -1 for Paris. 
> Similar to bloomfilter, min/max evaluation should use DateWritable (as DateWritable.compareTo uses days offset). 



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