You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2013/04/29 04:10:16 UTC

[jira] [Created] (HBASE-8454) TestImportTsv failing due to configuration issues

Andrew Purtell created HBASE-8454:
-------------------------------------

             Summary: TestImportTsv failing due to configuration issues
                 Key: HBASE-8454
                 URL: https://issues.apache.org/jira/browse/HBASE-8454
             Project: HBase
          Issue Type: Sub-task
          Components: mapreduce, test
    Affects Versions: 0.98.0, 0.94.8, 0.95.1
            Reporter: Andrew Purtell
            Assignee: Andrew Purtell


It looks like TestImportTsv can be fixed once HBASE-8453 is applied with this additional delta:

{noformat}
diff --git a/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java b/src/test/java/org/
index 77d044b..0da6f0a 100644
--- a/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
+++ b/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java
@@ -26,6 +26,7 @@ import java.util.ArrayList;
 import org.apache.commons.logging.Log;
 import org.apache.commons.logging.LogFactory;
 import org.apache.hadoop.hbase.*;
+import org.apache.hadoop.mapred.JobConf;
 import org.apache.hadoop.mapreduce.Job;
 import org.apache.hadoop.fs.FSDataOutputStream;
 import org.apache.hadoop.fs.Path;
@@ -289,7 +290,10 @@ public class TestImportTsv {
         LOG.info("set the hbaseAdmin");
         ImportTsv.createHbaseAdmin(conf);
       }
-      Job job = ImportTsv.createSubmittableJob(conf, args);
+
+      JobConf jobConf = htu1.getMRCluster().createJobConf();
+      HBaseConfiguration.merge(jobConf, conf);
+      Job job = ImportTsv.createSubmittableJob(jobConf, args);
       job.waitForCompletion(false);
       assertTrue(job.isSuccessful());
{noformat}

Tested with Hadoop 2.0.4 + HBase 0.94.7.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira