[DRILL-8423] Parquet TIME_MICROS columns with values > Integer.MAX_VALUE are not displayed correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.21.0
• Fix Version/s: 1.21.1
• Component/s: Storage - Parquet
• Assignee: Unassigned
• Reporter: Peter Franzen
• Created: 13/Apr/23 08:42
• Updated: 19/Apr/23 08:38
• Resolved: 19/Apr/23 08:38

Description

Assume a parquet file in a directory "Test" with a column timeCol having the type org.apache.parquet.schema.OriginalType.TIME_MICROS.

Assume there are two records with the values 2147483647 and 2147483648, respectively, in that column (i.e. the times 00:35:47.483647 and 00:35:47.483648).

Executing the query

SELECT timeCol FROM dfs.Test;

produces the result

timeCol
-------
00:35:47.483
23:24:12.517

i.e. the microsecond value of Integer.MAX_VALUE + 1 has wrapped around when read from the parquet file (it is displayed as the same number of milliseconds before midnight as the time represented by Integer.MAX_VALUE is after midnight)

 

Issue Links

• is related to: DRILL-8421 Parquet TIMESTAMP_MICROS columns in WHERE clauses are not converted to milliseconds before filtering