hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-730) Local file system uses copy to implement rename
Date Sun, 10 Feb 2008 09:09:07 GMT

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

Chris Douglas updated HADOOP-730:

    Attachment: 730-1.patch

Replaced calls to FileSystem::isDirectory() with FileSystem::getFileStatus().isDir() to resolve
the deprecation warnings. This doesn't need new unit tests because the existing ones cover
the semantics for rename. The core test that failed on Hudson passes on my machine.

> Local file system uses copy to implement rename
> -----------------------------------------------
>                 Key: HADOOP-730
>                 URL: https://issues.apache.org/jira/browse/HADOOP-730
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.8.0
>            Reporter: Owen O'Malley
>            Assignee: Chris Douglas
>             Fix For: 0.16.1
>         Attachments: 730-0.patch, 730-1.patch
> There is a variable LocalFileSystem.useCopyForRename that is set to true. When true,
the local file system will implement rename as a copy followed by a delete. This is likely
a performance problem. Is there a reason that useCopyForRename is set?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message