[
https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161978#comment-16161978
]
ASF GitHub Bot commented on DRILL-5377:
---------------------------------------
Github user vdiravka commented on the issue:
https://github.com/apache/drill/pull/916
@paul-rogers
There is no bug with corrupt Parquet dates, it was fixed in context of
DRILL-4203.
This commit fixes representing of the five digit year dates and doesn't
change logic for the 4(3,2...) digit year dates. It is made in similar manner
as TimePrintMillis.
But the best solution is to use necessary formatting. I am working on this,
so this PR can be closed.
> 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
> Labels: ready-to-commit
> 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)
