Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <32899786.1202943915889.JavaMail.jira@brutus>
Date: Wed, 13 Feb 2008 15:05:15 -0800 (PST)
From: "Chris Douglas (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-730) Local file system uses copy to
 implement rename
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Douglas updated HADOOP-730:
---------------------------------

    Status: Open  (was: Patch Available)

> 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: Improvement
>          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.