[jira] [Comment Edited] (HIVE-26233) Problems reading back PARQUET timestamps above 10000 years

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-26233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541969#comment-17541969 ] 

Stamatis Zampetakis edited comment on HIVE-26233 at 5/25/22 10:50 AM:
----------------------------------------------------------------------

Based on the git history I suspect the problem here starts appearing after HIVE-20007 although I haven't tried to repeat the test on that commit.


was (Author: zabetak):
I suspect the problem here starts appearing after HIVE-20007 although I haven't confirmed this.

> Problems reading back PARQUET timestamps above 10000 years
> ----------------------------------------------------------
>
>                 Key: HIVE-26233
>                 URL: https://issues.apache.org/jira/browse/HIVE-26233
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Peter Vary
>            Assignee: Peter Vary
>            Priority: Major
>              Labels: backwards-compatibility, pull-request-available, timestamp
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Timestamp values above year 10000 are not supported, but during the migration from Hive2 to Hive3 some might appear because of TZ issues. We should be able to at least read these tables before rewriting the data.
> For this we need to change the Timestamp.PRINT_FORMATTER, so no {{+}} sign is appended to the timestamp if the year exceeds 4 digits.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)