hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-3218) getRecordWriter need not to check the existence of the output directory
Date Thu, 29 Dec 2011 06:04:30 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harsh J resolved HADOOP-3218.
-----------------------------

    Resolution: Won't Fix

This shouldn't be removed, given Amareshwari's comment.
                
> getRecordWriter need not to check the existence of the output directory
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-3218
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3218
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Runping Qi
>
> I don't think the code segment in
> {code}
>     if (!fs.exists(outputPath)) {
>       throw new IOException("Output directory doesnt exist");
>     }
> {code} 
> is necessary.
> It actually cause unnecessary load to dfs namenode.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message