[jira] [Closed] (IMPALA-5942) Dateless timestamps (e.g. "10:00:00") are handled inconsistently

["Gabor Kaszab (Jira)" <ji...@apache.org>]

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

Gabor Kaszab closed IMPALA-5942.
--------------------------------
    Fix Version/s: Not Applicable
       Resolution: Won't Fix

Instead of making dateless timestamp consistent across all file formats we dropped the support of such in IMPALA-9531
For the reasoning see the discussion on this ticket.

> Dateless timestamps (e.g. "10:00:00") are handled inconsistently 
> -----------------------------------------------------------------
>
>                 Key: IMPALA-5942
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5942
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.11.0
>            Reporter: Csaba Ringhofer
>            Priority: Major
>              Labels: timestamp
>             Fix For: Not Applicable
>
>
> Impala cannot read back these timestamps from Parquet, while it  can read them back from textfiles.
> According to the documentation, Impala should be able to handle these values somehow, as the examples contain "select cast('08:30:00' as timestamp);"
> see http://impala.apache.org/docs/build/html/topics/impala_timestamp.html 
> {code}
> text:
> create table TT1 (t timestamp);
> insert into TT1 (t) values ("10:00:00");
> select * from TT1;
> +----------+
> | t        |
> +----------+
> | 10:00:00 |
> +----------+
> parquet:
> create table TT2(t timestamp) STORED AS PARQUET;
> insert into TT2 (t) values ("10:00:00");
> select * from TT2;
> +------+
> | t    |
> +------+
> | NULL |
> +------+
> WARNINGS: Parquet file 'hdfs://localhost:20500/test-warehouse/tt2/714d741212df3180-cd4e670800000000_226739479_data.0.parq' column 't' contains an out of range timestamp. The valid date range is 1400-01-01..9999-12-31.
> {code}
> I think that this is a side effect of the fix of IMPALA-4363, but I did not check what happens in versions that did not contain this fix.
> UPDATE: I have checked the last commit before the fix of  IMPALA-4363, and it does not have this bug.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)