You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/07/24 22:51:49 UTC
[jira] [Resolved] (HADOOP-9767) RawLocalFileSystem#rename does not
correctly enforce replacement of empty destination directory on all
platforms
[ https://issues.apache.org/jira/browse/HADOOP-9767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth resolved HADOOP-9767.
-----------------------------------
Resolution: Duplicate
I just realized that this is basically a duplicate of HADOOP-9507, so I'll post patches over there.
> RawLocalFileSystem#rename does not correctly enforce replacement of empty destination directory on all platforms
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-9767
> URL: https://issues.apache.org/jira/browse/HADOOP-9767
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 3.0.0, 1-win, 2.1.0-beta, 1.3.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
>
> POSIX {{rename}} semantics state that renaming a source directory to an existing destination directory that is empty will act as a full replacement of that existing destination. {{RawLocalFileSystem#rename}} calls Java's {{File#renameTo}}, which provides these semantics on most platforms. On some platforms (notably Windows), {{File#renameTo}} does not provide this behavior. This causes problems for MapReduce and other downstream components like Hive, HCatalog, and Sqoop that depend on the replacement behavior.
--
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