hadoop-common-issues mailing list archives

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

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

Doug Cutting commented on HADOOP-6240:
--------------------------------------

Suresh> all the behaviors I documented in my previous comment are different

Thanks.  I mostly meant to be asking which of the new behaviors will cause problems for applications
if we implement them generically, mandating FileSystem-specific implementations?  All of them?
 None of them?

Sanjay> atomic if fs supports it and is within the same partition

And if an FS does not implement it atomically, should it be an error, or just not atomic?
 If not atomic, that may create some confusion, no?

Sanjay> a partitioned scalable hdfs does not do the rename atomically (symlink is the only
option here)

Then perhaps we should encourage all applications to use symlinks as the fundamental, reliable,
atomic overwriting rename?

We'd like to have a single, preferred idiom for atomic updates that we suggest applications
use.  If an application wishes to make atomic updates, it should use a single mechanism, regardless
of the FileSystem it's writing to, no?


> 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