[
https://issues.apache.org/jira/browse/MAPREDUCE-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915904#comment-13915904
]
Steve Loughran commented on MAPREDUCE-5264:
-------------------------------------------
mark up as related to HADOOP-9361 as a diff between filesystem contract and
expected behaviour downstream
> FileAlreadyExistsException is assumed to be thrown by FileSystem#mkdirs or
> FileContext#mkdir in the codebase
> ------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5264
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5264
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Rémy SAISSY
> Attachments: MAPREDUCE-5264.20130607.1.patch
>
>
> According to https://issues.apache.org/jira/browse/HADOOP-9438,
> FileSystem#mkdirs and FileContext#mkdir do not throw
> FileAlreadyExistsException if the directory already exist.
> Some places in the mapreduce codebase assumes FileSystem#mkdirs or
> FileContext#mkdir throw FileAlreadyExistsException.
> At least the following files are concerned:
> - YarnChild.java
> - JobHistoryEverntHandler.java
> - HistoryFileManager.java
> It would be good to re-review and patch this if needed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
