[HIVE-3454] Problem with CAST(BIGINT as TIMESTAMP)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0, 0.8.1, 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.13.0, 0.13.1
• Fix Version/s: 1.2.0
• Component/s: Types, UDF
• Labels: newbie newdev patch
• Hadoop Flags: Incompatible change

Release Note

The behaviors of converting from BOOLEAN/TINYINT/SMALLINT/INT/BIGINT and converting from FLOAT/DOUBLE to TIMESTAMP were inconsistent. The value of a BOOLEAN/TINYINT/SMALLINT/INT/BIGINT was treated as the time in milliseconds while the value of a FLOAT/DOUBLE was treated as the time in seconds. After the change, all the types during the conversion are interpreted in seconds.

• Tags: timestamp
• Assignee: Aihua Xu
• Reporter: Ryan Harris
• Created: 12/Sep/12 22:40
• Updated: 23/Nov/15 19:26
• Resolved: 24/Mar/15 18:24

Description

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.

Issue Links

• is depended upon by: HIVE-9917 After HIVE-3454 is done, make int to timestamp conversion configurable
• is duplicated by: HIVE-3822 Casting from double to timestamp type seems inconsistent
• is related to: HIVE-11168 Followup on HIVE-9917, set the default value of hive.int.timestamp.conversion.in.seconds to true