[jira] [Commented] (HIVE-6581) vectorization_decimal_date.q is dependent on local host timezone
[ https://issues.apache.org/jira/browse/HIVE-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923854#comment-13923854 ] Remus Rusanu commented on HIVE-6581: Agreed, I reolved as duplicate of HIVE-5175 > vectorization_decimal_date.q is dependent on local host timezone > > > Key: HIVE-6581 > URL: https://issues.apache.org/jira/browse/HIVE-6581 > Project: Hive > Issue Type: Test >Reporter: Remus Rusanu >Assignee: Teddy Choi >Priority: Minor > > Running vectorization_decimal_date.q fails in eastern hemisphere due to > result diffs. In my GMT+2 zone, the first column returns "1970-01-07". This > comes from the CAST (CAST (cint AS TIMESTAMP) AS DATE) AS cdate expression > in the CTAS, this returns different dates on depending on local timezone (in > row-mode, this is not a vectorization issue). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6581) vectorization_decimal_date.q is dependent on local host timezone
[ https://issues.apache.org/jira/browse/HIVE-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923810#comment-13923810 ] Thejas M Nair commented on HIVE-6581: - This is probably related to HIVE-5175 . This is probably not the only unit test that would fail on windows machine with non pacific timezone. > vectorization_decimal_date.q is dependent on local host timezone > > > Key: HIVE-6581 > URL: https://issues.apache.org/jira/browse/HIVE-6581 > Project: Hive > Issue Type: Test >Reporter: Remus Rusanu >Assignee: Teddy Choi > > Running vectorization_decimal_date.q fails in eastern hemisphere due to > result diffs. In my GMT+2 zone, the first column returns "1970-01-07". This > comes from the CAST (CAST (cint AS TIMESTAMP) AS DATE) AS cdate expression > in the CTAS, this returns different dates on depending on local timezone (in > row-mode, this is not a vectorization issue). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6581) vectorization_decimal_date.q is dependent on local host timezone
[ https://issues.apache.org/jira/browse/HIVE-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923792#comment-13923792 ] Remus Rusanu commented on HIVE-6581: [~thejas] It has no effect if you run the tests on Windows. > vectorization_decimal_date.q is dependent on local host timezone > > > Key: HIVE-6581 > URL: https://issues.apache.org/jira/browse/HIVE-6581 > Project: Hive > Issue Type: Test >Reporter: Remus Rusanu >Assignee: Teddy Choi > > Running vectorization_decimal_date.q fails in eastern hemisphere due to > result diffs. In my GMT+2 zone, the first column returns "1970-01-07". This > comes from the CAST (CAST (cint AS TIMESTAMP) AS DATE) AS cdate expression > in the CTAS, this returns different dates on depending on local timezone (in > row-mode, this is not a vectorization issue). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6581) vectorization_decimal_date.q is dependent on local host timezone
[ https://issues.apache.org/jira/browse/HIVE-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923788#comment-13923788 ] Thejas M Nair commented on HIVE-6581: - AFAIK, the build/test scripts are supposed to set the timezone to US/Pacific for consistent results. I see that pom.xml setsUS/Pacific. > vectorization_decimal_date.q is dependent on local host timezone > > > Key: HIVE-6581 > URL: https://issues.apache.org/jira/browse/HIVE-6581 > Project: Hive > Issue Type: Test >Reporter: Remus Rusanu >Assignee: Teddy Choi > > Running vectorization_decimal_date.q fails in eastern hemisphere due to > result diffs. In my GMT+2 zone, the first column returns "1970-01-07". This > comes from the CAST (CAST (cint AS TIMESTAMP) AS DATE) AS cdate expression > in the CTAS, this returns different dates on depending on local timezone (in > row-mode, this is not a vectorization issue). -- This message was sent by Atlassian JIRA (v6.2#6252)
