[
https://issues.apache.org/jira/browse/DRILL-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Franzen updated DRILL-8423:
---------------------------------
Affects Version/s: 1.21.0
(was: 1.20.3)
> Parquet TIME_MICROS columns with values > Integer.MAX_VALUE are not displayed
> correctly
> ---------------------------------------------------------------------------------------
>
> Key: DRILL-8423
> URL: https://issues.apache.org/jira/browse/DRILL-8423
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
> Affects Versions: 1.21.0
> Reporter: Peter Franzen
> Priority: Major
>
> 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
> {code:java}
> SELECT timeCol FROM dfs.Test;{code}
> produces the result
> {code:java}
> timeCol
> -------
> 00:35:47.483
> 23:24:12.517{code}
> 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)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
