You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jimmy Xiang (JIRA)" <ji...@apache.org> on 2012/05/10 20:36:49 UTC

[jira] [Updated] (HBASE-5985) TestMetaMigrationRemovingHTD failed with HADOOP 2.0.0

     [ https://issues.apache.org/jira/browse/HBASE-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jimmy Xiang updated HBASE-5985:
-------------------------------

    Status: Patch Available  (was: Open)

In HADOOP 2.0.0, -put doesn't create parent directory automatically, the fix is to create the parent directory before -put if it is not there.
                
> TestMetaMigrationRemovingHTD failed with HADOOP 2.0.0
> -----------------------------------------------------
>
>                 Key: HBASE-5985
>                 URL: https://issues.apache.org/jira/browse/HBASE-5985
>             Project: HBase
>          Issue Type: Test
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>             Fix For: 0.96.0
>
>         Attachments: hbase-5985.patch
>
>
> -------------------------------------------------------------------------------
> Test set: org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.448 sec <<< FAILURE!
> org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD  Time elapsed: 0 sec  <<< ERROR!
> java.io.IOException: Failed put; errcode=1
>     at org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD.doFsCommand(TestMetaMigrationRemovingHTD.java:124)
>     at org.apache.hadoop.hbase.client.TestMetaMigrationRemovingHTD.setUpBeforeClass(TestMetaMigrationRemovingHTD.java:80)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:597)
>     at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>     at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>     at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>     at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
>     at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>     at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>     at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
>     at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira