[
https://issues.apache.org/jira/browse/HIVE-21067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730234#comment-16730234
]
Andrey Zinovyev commented on HIVE-21067:
----------------------------------------
Well it is not that easy to read sql standard apparently (its not publicly
available). But in major implemetations (like ms sql and postgre) timestamp
functions return values in user tz as far as I can tell. Especially in case of
timestamp without tz.
> TO_UNIX_TIMESTAMP (or UNIX_TIMESTAMP) treats argument timestamp as UTC
> ----------------------------------------------------------------------
>
> Key: HIVE-21067
> URL: https://issues.apache.org/jira/browse/HIVE-21067
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Andrey Zinovyev
> Priority: Minor
>
> In previous versions (at least in 1.2) we had
> > SELECT TO_UNIX_TIMESTAMP("2018-12-25 02:00:53.297");
> 1545692453
> Now it is
> > SELECT TO_UNIX_TIMESTAMP("2018-12-25 02:00:53.297");
> 1545703253
> We're in +3 timezone (Europe/Moscow)
> This changes was made in HIVE-12192. I don't know if it was intentional, but
> according to
> [wiki|https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-DateFunctions]
> unix_timestamp should use default timezone
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
