[jira] [Commented] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

["Arina Ielchiieva (JIRA)" <ji...@apache.org>]

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

Arina Ielchiieva commented on DRILL-5377:
-----------------------------------------

[~vitalii] after upgrade to Calcite 1.15 year with more then 4 digits is disallowed according to Sql standard.

[~vvysotskyi] please confirm.

> 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
>            Priority: Minor
>             Fix For: 1.13.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
(v7.6.3#76005)