[ https://issues.apache.org/jira/browse/HIVE-25323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381338#comment-17381338 ]
Karen Coppage commented on HIVE-25323: -------------------------------------- [~adeshrao] thanks for taking a look! Probably the reason java.sql.Timestamp was left in vectorization is lost to time. Until the fix is done – and I assume it will be a bit of time – we can re-enable the test, convert the timestamps from java.sql.Timestamp -> hive.Timestamp and then compare. By the way do you know why the test was timing out after 5h instead of failing? > Fix TestVectorCastStatement > --------------------------- > > Key: HIVE-25323 > URL: https://issues.apache.org/jira/browse/HIVE-25323 > Project: Hive > Issue Type: Task > Reporter: Karen Coppage > Assignee: Adesh Kumar Rao > Priority: Major > > org.apache.hadoop.hive.ql.exec.vector.expressions.TestVectorCastStatement > tests were timing out after 5 hours. > [http://ci.hive.apache.org/job/hive-flaky-check/307/] > First failure: > [http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/master/749/pipeline/242] -- This message was sent by Atlassian Jira (v8.3.4#803005)