You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Greg Rahn (Jira)" <ji...@apache.org> on 2019/10/05 00:03:00 UTC

[jira] [Resolved] (IMPALA-2860) allow Impala to interpret "0001-01-01" and later as a date

     [ https://issues.apache.org/jira/browse/IMPALA-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Rahn resolved IMPALA-2860.
-------------------------------
    Resolution: Fixed

> 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)