[
https://issues.apache.org/jira/browse/MAPREDUCE-6512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235290#comment-15235290
]
Hadoop QA commented on MAPREDUCE-6512:
--------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color}
| {color:red} MAPREDUCE-6512 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12770101/MAPREDUCE-6512.2.patch
|
| JIRA Issue | MAPREDUCE-6512 |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/6427/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> FileOutputCommitter tasks unconditionally create parent directories
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-6512
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6512
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Eric Badger
> Attachments: MAPREDUCE-6512.2.patch, MAPREDUCE-6512.2.patch,
> MAPREDUCE-6512.patch, MAPREDUCE-6512.patch
>
>
> If the output directory is deleted then subsequent tasks should fail. Instead
> they blindly create the missing parent directories, leading the job to be
> "succesful" despite potentially missing almost all of the output. Task
> attempts should fail if the parent app attempt directory is missing when they
> go to create their task attempt directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
