hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Harris (JIRA)" <>
Subject [jira] [Commented] (HIVE-3454) Problem with CAST(BIGINT as TIMESTAMP)
Date Sat, 05 Jan 2013 09:52:12 GMT


Ryan Harris commented on HIVE-3454:

After commenting on HIVE-3822 I've realized that even with this quasi-workaround, the cast(int/float/double
as timestamp) is fundamentally broken.
When an epoch (assumed GMT) timestamp is passed through the cast() function it is converted
to a different time based on the local timezone...this doesn't happen if the timestamp is
cast from a formatted date string....this behavior is inconsistent.

Furthermore, when attempting to use the to_utc_timestamp() function with a epoch date value
the implicit cast() poisons the result of the timestamp that is stored by to_utc_timestamp()

Something is definitely wrong.
> Problem with CAST(BIGINT as TIMESTAMP)
> --------------------------------------
>                 Key: HIVE-3454
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Types, UDF
>    Affects Versions: 0.9.0
>            Reporter: Ryan Harris
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message