[
https://issues.apache.org/jira/browse/IMPALA-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944923#comment-16944923
]
Greg Rahn commented on IMPALA-2860:
-----------------------------------
Solved in IMPALA-6169 which adds DATE type.
> allow Impala to interpret "0001-01-01" and later as a date
> ----------------------------------------------------------
>
> Key: IMPALA-2860
> URL: https://issues.apache.org/jira/browse/IMPALA-2860
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.2.2
> Reporter: Boris Gitline
> Priority: Minor
>
> scenario:
> create table foo
> stored as parquet
> as
> select cast('0001-01-01 00:00:00' as timestamp) ts;
> result:
> Year is out of valid range: 1400..10000
> importing lots of data from mainframe systems; the default date on these
> mainframes is "0001-01-01". As it is, when impala interprets these dates into
> a timestamp field, it is converted to null.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
