[ 
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624073#comment-13624073
 ] 

Jonathan Hsieh commented on HBASE-8258:
---------------------------------------

bq. Why is do we need to override these in our minimrcluster tests?
bq. Why isn't this a problem on other HBase-MR jobs?

The other MR tests use the HBaseTestingUtility's getConfiguration conf.  When 
the mini-mr cluster is started it adds values to it.  The current 
TestImportExport gets the values from 
HBaseTestingUtility.getMiniCluster.getConf which does not have yarn/mr values 
added.  That's why we had to the extra copy junk.

If we use the pattern used in the other MR jobs, we don't have this problem.  
There is one catch -- we need to make a "copy" of the conf for the job conf by 
using new Configuration(htu.getConfiguration).  Without that I was having data 
from previous exports from one test interfere with subsequent runs in suite.

bq. Why isn't this need documented and where should it be?
bq. What can we do to properly propagate this so that future MR tests won't 
have this problem?

I will improve javadoc in HBaseTestingUtility to explain the proper way of 
getting configurations for hbase unit test mr jobs.
                
> Make mapreduce tests pass on hadoop2
> ------------------------------------
>
>                 Key: HBASE-8258
>                 URL: https://issues.apache.org/jira/browse/HBASE-8258
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.95.1
>
>         Attachments: 8258-plain.txt, 8258-v1-hadoop-2.0.txt, 
> 8258-v2-hadoop-2.0.txt, 8258-v4-hadoop-2.0.txt
>
>
> HBASE-7904 was a first attempt at making this work but it got lost in the 
> weeds.
> This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o 
> breaking mapreduce on hadoop1)

--
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

Reply via email to