[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624088#comment-13624088
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
[~ndimiduk] That is very close the explanation that I have. The minimrcluster
for yarn adds values to the configuration so if we refer to the same one and
copy it later, we get the updated yarn settings. This is what all the other MR
tests do.
I need to look into why we need to do the copy of the config to prevent
interference (likely some if the value is set don't update it logic).
I agree that using the tool interface makes sense as well -- feels like a nice
follow up issue.
I've been running with the version I posted on trunk against hadoop 2.0 -- will
report on that and against hadoop 1.0 when results return.
> 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-8258-simple.patch
>
>
> 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
