hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-654) HDFS needs to support new rename introduced for FileContext
Date Mon, 28 Sep 2009 00:51:16 GMT

    [ https://issues.apache.org/jira/browse/HDFS-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760132#action_12760132
] 

dhruba borthakur commented on HDFS-654:
---------------------------------------

Thanks for the explanation. I was referring to the check in FSNameSystem.checkFsObjectLimit()
that checks the total number of inodes in the FS. I was worried that you allow replacing a
non-empty directory with an empty directory in which case the totalInode in the FS has to
be adjusted accordingly. 

> HDFS needs to support new rename introduced for FileContext
> -----------------------------------------------------------
>
>                 Key: HDFS-654
>                 URL: https://issues.apache.org/jira/browse/HDFS-654
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 0.21.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: hdfs-654.1.patch, HDFS-654.patch
>
>
> New rename functionality with different semantics to overwrite the existing destination
was introduced for use in FileContext. Currently the default implementation in FileSystem
is not atomic. This change implements atomic rename operation for use by FileContext.

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