hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6240) Rename operation is not consistent between different implementations of FileSystem
Date Mon, 14 Sep 2009 17:58:57 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755107#action_12755107
] 

Konstantin Shvachko commented on HADOOP-6240:
---------------------------------------------

It was probably too general for me to say "We should not provide atomic renames".
What I meant is not to extend implementation of atomic rename to the case when the destination
exists.
So I am advocating to keep current semantics of renames in hdfs.
{{LocalFileSystem}} may do the same, this will make it consistent with hdfs.
And this is the only thing this issue should do.
Is there a use case, when atomic rename replacing the existing destination is required?

> Rename operation is not consistent between different implementations of FileSystem
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-6240
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6240
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.21.0
>
>
> The rename operation has many scenarios that are not consistently implemented across
file systems.

-- 
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