[
https://issues.apache.org/jira/browse/MAPREDUCE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538403#comment-13538403
]
Robert Kanter commented on MAPREDUCE-4898:
------------------------------------------
I just ran all of the tests under {{hadoop-mapreduce-project}} successfully.
I also just checked where those two methods are used and there's no issues
because:
1) Whenever {{checkOutputSpecs}} is used, the code handles an {{IOException}}
instead of either of the two types of {{FileAlreadyExistsException}}, and both
types of {{FileAlreadyExistsException}} inherit from {{IOException}}
2) Whenever {{setOutputPath}} is used, there's always other method calls that
can throw {{IOException}}s anyway
> 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.3-alpha
>
> 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
