[
https://issues.apache.org/jira/browse/HIVE-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347582#comment-14347582
]
Gunther Hagleitner commented on HIVE-3454:
------------------------------------------
I agree with [~sershe]. These statics aren't just a pain w/ multi threading,
they also hurt if you just re-use the same jvm for multiple things. This can
happen in tez, spark and if we decide to run stuff on the client/in hs2 afaik.
More specifically though: This config should take effect at compile time. There
is no reason to evaluate the condition for each value in each row at run time.
We should be able to just install the appropriate udf when we compile the
query, no?
> Problem with CAST(BIGINT as TIMESTAMP)
> --------------------------------------
>
> Key: HIVE-3454
> URL: https://issues.apache.org/jira/browse/HIVE-3454
> Project: Hive
> Issue Type: Bug
> Components: Types, UDF
> Affects Versions: 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0,
> 0.13.1
> Reporter: Ryan Harris
> Assignee: Aihua Xu
> Labels: newbie, newdev, patch
> Attachments: HIVE-3454.1.patch.txt, HIVE-3454.2.patch,
> HIVE-3454.3.patch, HIVE-3454.4.patch, HIVE-3454.patch
>
>
> Ran into an issue while working with timestamp conversion.
> CAST(unix_timestamp() as TIMESTAMP) should create a timestamp for the current
> time from the BIGINT returned by unix_timestamp()
> Instead, however, a 1970-01-16 timestamp is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
