[
https://issues.apache.org/jira/browse/MAPREDUCE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635338#comment-13635338
]
Robert Kanter commented on MAPREDUCE-4898:
------------------------------------------
I created a job like you said and ran it on Hadoop 1 and Hadoop 2 with and
without setting the working dir. The behavior is the same in both Hadoop 1 and
Hadoop 2: without setting the working dir, it resolves a relative path to the
homedir; with setting the working dir, it resolves a relative path to that dir
(even in Hadoop 1). So no behavioral change here :)
> FileOutputFormat.checkOutputSpecs and FileOutputFormat.setOutputPath
> incompatible with MR1
> ------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4898
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4898
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: 2.0.5-beta
>
> Attachments: MAPREDUCE-4898.patch
>
>
> In MR1,
> {{org.apache.hadoop.mapreduce.lib.output.FileOutputFormat.checkOutputSpecs}}
> throws {{org.apache.hadoop.mapred.FileAlreadyExistsException}} but now it
> throws {{org.apache.hadoop.fs.FileAlreadyExistsException}} instead, making
> them incompatible.
> In MR1,
> {{org.apache.hadoop.mapreduce.lib.output.FileOutputFormat.setOutputPath}}
> doesn't throw any exceptions but now it throws an {{IOException}}, making
> them incompatible.
--
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
