[
https://issues.apache.org/jira/browse/HIVE-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761836#comment-16761836
]
paco87 commented on HIVE-21121:
-------------------------------
It appears that this issue has problems when timezone is set (maybe due to
summer/winter time) if UTC is 0 everything works fine.
I checked two timezones Europe/Warsaw and Europe/Kiove diffrent dates have this
problem.
> Cast date to timestamp incorrect interpretation
> -----------------------------------------------
>
> Key: HIVE-21121
> URL: https://issues.apache.org/jira/browse/HIVE-21121
> Project: Hive
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.2.1, 2.1.0
> Reporter: paco87
> Priority: Major
> Attachments: jira_replicate_issue.txt
>
>
> Hive is returning timestamp with current time when casting date to timestamp,
> where it should be 00:00:00.0 .
> This issue is wired. It seems that this happens only on specific date:
> '1900-01-01'.
> +----------------------------++
> |ab|
> +----------------------------++
> |1900-01-01 11:28:46.869|
> |1900-01-01 11:28:46.869|
> |1900-01-01 11:28:46.869|
> |1900-01-01 11:28:46.869|
> |1890-01-01 00:00:00.0|
> |1901-01-01 00:00:00.0|
> |1900-01-01 11:28:46.869|
> +---------------------------++
> I didin't notice this on any other date.
> This might be connected to old issue: HIVE-10488
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
