You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2014/12/11 19:43:13 UTC
[jira] [Commented] (MAPREDUCE-4879) TeraOutputFormat may overwrite
an existing output directory
[ https://issues.apache.org/jira/browse/MAPREDUCE-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242927#comment-14242927 ]
Chris Nauroth commented on MAPREDUCE-4879:
------------------------------------------
Hi, [~jira.shegalov]. This looks good. Could you please throw {{FileAlreadyExistsException}} instead of {{IOException}}? That would exactly match the behavior of {{FileOutputFormat}} when it checks the output directory. Thanks!
> TeraOutputFormat may overwrite an existing output directory
> -----------------------------------------------------------
>
> Key: MAPREDUCE-4879
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4879
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: examples
> Affects Versions: trunk
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: MAPREDUCE-4879-trunk-rev1.patch, MAPREDUCE-4879-trunk.patch
>
>
> Unlike FileOutputFormat, TeraOutputFormat does not prevent TeraGen/Sort jobs from writing into an existing directory, and potentially overwriting previous runs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)