[HIVE-3822] Casting from double to timestamp type seems inconsistent

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.9.0
• Assignee: Unassigned
• Reporter: Mark Grover
• Created: 19/Dec/12 19:36
• Updated: 08/Apr/17 19:51

Description

select cast(1355944339 as timestamp) from decimal_3 limit 1;
1970-01-16 08:39:04.339

select cast(1355944339000 as timestamp) from decimal_3 limit 1;
2012-12-19 11:12:19

select cast(1355944339.123456789 as timestamp) from decimal_3 limit 1;
2012-12-19 11:12:19.1234567

If specifying the unixTimestamp without a decimal point, we need to specify the millisecond timestamp. If specifying with a decimal point, we need to specify only the second timestamp and the rest goes after decimal. Moreover, it seems like some precision is lost (notice '89' are lost in the last query.

Issue Links

• duplicates: HIVE-3454 Problem with CAST(BIGINT as TIMESTAMP)
• is related to: HIVE-3844 Unix timestamps don't seem to be read correctly from HDFS as Timestamp column