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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: Impala 2.11.0
• Fix Version/s: Not Applicable
• Component/s: Backend
• Labels: timestamp
• Target Version: Product Backlog
• Epic Color: ghx-label-1
• Assignee: Unassigned
• Reporter: Csaba Ringhofer
• Created: 15/Sep/17 16:35
• Updated: 22/Jul/20 08:20
• Resolved: 22/Jul/20 08:20

Description

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

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.

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.

Issue Links

• is broken by: IMPALA-4363 SELECTing invalid timestamp value from Parquet file crashes impalad
• is related to: IMPALA-9531 Drop support for "dateless timestamps"
• relates to: IMPALA-5983 Dateless timestamps (e.g. "10:00:00") can cause crash during timezone conversion