Gordon Wang created HIVE-6244:
---------------------------------
Summary: hive UT fails on top of Hadoop 2.2.0
Key: HIVE-6244
URL: https://issues.apache.org/jira/browse/HIVE-6244
Project: Hive
Issue Type: Bug
Components: Shims
Affects Versions: 0.12.0
Reporter: Gordon Wang
When building hive 0.12.0 on top of hadoop 2.2.0, a lot of UT fails. The error
messages are like this.
{code}
Job Submission failed with exception 'java.lang.IllegalArgumentException(Wrong
FS:
pfile:/home/pivotal/jenkins/workspace/Hive0.12UT_withJDK7/build/ql/test/data/warehouse/src,
expected: file:///)'
junit.framework.AssertionFailedError: Client Execution failed with error code =
1
See build/ql/tmp/hive.log, or try "ant test ... -Dtest.silent=false" to get
more logs.
at junit.framework.Assert.fail(Assert.java:50)
at
org.apache.hadoop.hive.cli.TestCliDriver.runTest(TestCliDriver.java:6697)
at
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_join_empty(TestCliDriver.java:3807)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:520)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1060)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:911)
{code}
listLocatedStatus is not implemented in Hive shims. I think this is the root
cause.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
