[IMPALA-1435] unix_timestamp() default timezone different from Hive or MySQL

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 1.4.1
• Fix Version/s: Impala 2.2
• Labels: ramp-up
• Assignee: casey
• Reporter: Julien Lehuen
• Created: 30/Oct/14 13:56
• Updated: 04/Jan/17 23:58
• Resolved: 25/Feb/15 23:05

Description

For the sake of demonstration, let's say I try to call unix_timestamp('2014-10-10 10:13:00') in both Hive and Impala. I get two different timestamps:

• Hive: 1412928780
• Impala: 1412935980

Now if I try to look in a third (standard) place what these two timestamps correspond to, it seems to me like Hive is right. I looked in MySQL:

mysql> select from_unixtime('1412928780') as 'Hive 1412928780'
            , from_unixtime('1412935980') as 'Impala 1412935980';

Hive 1412928780	Impala 1412935980
2014-10-10 10:13:00	2014-10-10 12:13:00

Interestingly, all these tests have been run in the same timezone (Europe/Amsterdam), which is 2 hours behind UTC time. It therefore feels as if Hive assumes the time string I give is in my Timezone, while Impala assumes that string is in the UTC Timezone.

It would be nice if Impala would align its behavior with MySQL and Hive.

Issue Links

• duplicates: IMPALA-97 Impala returns "1970-01-01 00:00:00" in from_unixtime(0) , Hive returns "1970-01-01 09:00:00" in Japan