drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc
Date Wed, 13 Sep 2017 18:08:00 GMT

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

ASF GitHub Bot commented on DRILL-5377:
---------------------------------------

Github user paul-rogers commented on the issue:

    https://github.com/apache/drill/pull/916
  
    Other than dealing with corrupted dates from Parquet, what other uses of five digit years
are expected? Few business processes project 8,000 years into the future. Scientific projects
are likely to project far more than just 10,000 years into the future; they would need to
handle billions of years (death of the sun) to trillions (heat death of the universe.) By
contrast, 8000 years ago were civilizations that we no know only from a few archeological
remains. Few business records extend that far back.
    
    So, if not for corrupt Parquet dates, what is the use case for 5-digit years? Why is Drill
the only tool needing such dates? If they were common, wouldn't `java.sql.Date`, SQL, the
ISO standard and other mechanisms define the rules?


> Five-digit year dates are displayed incorrectly via jdbc
> --------------------------------------------------------
>
>                 Key: DRILL-5377
>                 URL: https://issues.apache.org/jira/browse/DRILL-5377
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Parquet
>    Affects Versions: 1.10.0
>            Reporter: Rahul Challapalli
>            Assignee: Vitalii Diravka
>             Fix For: 1.12.0
>
>
> git.commit.id.abbrev=38ef562
> The issue is connected to displaying five-digit year dates via jdbc
> Below is the output, I get from test framework when I disable auto correction for date
fields
> {code}
> select l_shipdate from table(cp.`tpch/lineitem.parquet` (type => 'parquet', autoCorrectCorruptDates
=> false)) order by l_shipdate limit 10;
> ^@356-03-19
> ^@356-03-21
> ^@356-03-21
> ^@356-03-23
> ^@356-03-24
> ^@356-03-24
> ^@356-03-26
> ^@356-03-26
> ^@356-03-26
> ^@356-03-26
> {code}
> Or a simpler case:
> {code}
> 0: jdbc:drill:> select cast('11356-02-16' as date) as FUTURE_DATE from (VALUES(1));
> +--------------+
> | FUTURE_DATE  |
> +--------------+
> | 356-02-16   |
> +--------------+
> 1 row selected (0.293 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message