Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 30 Dec 2014 03:11:13 +0000 (UTC)
From: "Yi Liu (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12764119.1419908933000.112899.1419909073874@Atlassian.JIRA>
In-Reply-To: <JIRA.12764119.1419908933000@Atlassian.JIRA>
References: <JIRA.12764119.1419908933000@Atlassian.JIRA>
 <JIRA.12764119.1419908933586@arcas>
Subject: [jira] [Updated] (HADOOP-11452) Revisit FileSystem#rename
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yi Liu updated HADOOP-11452:
----------------------------
    Summary: Revisit FileSystem#rename  (was: Revisit org.apache.hadoop.fs.FileSystem#rename)

> Revisit FileSystem#rename
> -------------------------
>
>                 Key: HADOOP-11452
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11452
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: fs
>            Reporter: Yi Liu
>            Assignee: Yi Liu
>
> Currently in {{FileSystem}}, {{rename}} with _Rename options_ is protected and with _deprecated_ annotation. And the default implementation is not atomic.
> So this method is not able to be used outside. On the other hand, HDFS has a good and atomic implementation. (Also an interesting thing in {{DFSClient}}, the _deprecated_ annotations for these two methods are opposite).
> It makes sense to make public for {{rename}} with _Rename options_, since it's atomic for rename+overwrite, also it saves RPC calls if user desires rename+overwrite.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)