[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625660#comment-13625660
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
Fully qualifying the export path to hdfs makes the job work in hadoop1.
In hadoop 1:
export was exporting to a "random" dir in hdfs, while import was expecting data
from the hadoop file system.
* export to:
hdfs://localhost:46368/user/jon/test-data/72b45ff2-9203-4791-aa28-2b95e44f5d95/hadoop/mapred-working-dir/outputdir/part-m-00000
h
* import from: hdfs://localhost:46368/user/jon/outputdir/
In hadoop 2:
export was exporting to the hdfs while import was expecting data form hdfs.
* export to: hdfs://localhost:60549/user/jon/outputdir/part-m-00000
* import from: hdfs://localhost:60549/user/jon/outputdir/
So at least for the export tests, I'm going to use fully qualified hdfs paths
for the export output
> 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
