[
https://issues.apache.org/jira/browse/HIVE-26233?focusedWorklogId=771309&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-771309
]
ASF GitHub Bot logged work on HIVE-26233:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/May/22 12:48
Start Date: 17/May/22 12:48
Worklog Time Spent: 10m
Work Description: pvary opened a new pull request, #3295:
URL: https://github.com/apache/hive/pull/3295
### What changes were proposed in this pull request?
Timestamps where the year is more than 4 digits will not have an extra +
sign in front of them
### Why are the changes needed?
So these big timestamps could be read and rewritten so they can conform the
original 9999 year limit.
### Does this PR introduce _any_ user-facing change?
Timestamps where the year is more than 4 digits will not have an extra +
sign in front of them. Since it was not supported even before this change, I
think it is ok to have this in.
### How was this patch tested?
Added unit test
Issue Time Tracking
-------------------
Worklog Id: (was: 771309)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> 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)
