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 Wed, 13 Feb 2008 23:05:09 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-2.patch

The rename code was removed from the patch to LocalFileSystem, since ChecksumFileSystem's
is sufficient (it was suspected that copying on rename was causing the crc to be regenerated
as part of the move, but that was mistaken). Since this doesn't patch a bug, I'm moving it
to 0.17. Without the bug fix, it's trivial enough that I don't think it needs a test case.
I also changed the ternary operator to an if/else stmt.

> 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.17.0
>
>         Attachments: 730-0.patch, 730-1.patch, 730-2.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.


Mime
View raw message