[
https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945457#comment-15945457
]
Vitalii Diravka commented on DRILL-5377:
----------------------------------------
sqlline usually cuts a years longer than 9999. In the drill's webui I've got
the following result:
{code}
l_shipdate
15356-03-19T00:00:00.000-07:00
15356-03-21T00:00:00.000-07:00
15356-03-21T00:00:00.000-07:00
15356-03-23T00:00:00.000-07:00
15356-03-24T00:00:00.000-07:00
15356-03-24T00:00:00.000-07:00
15356-03-26T00:00:00.000-07:00
15356-03-26T00:00:00.000-07:00
15356-03-26T00:00:00.000-07:00
15356-03-26T00:00:00.000-07:00
{code}
It looks like an expected result.
> Drill returns weird characters when parquet date auto-correction is turned off
> ------------------------------------------------------------------------------
>
> 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
>
> git.commit.id.abbrev=38ef562
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
