Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 13 Mar 2013 22:38:13 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12634353.1361937807252.437333.1363214293146@arcas>
In-Reply-To: <JIRA.12634353.1361937807252@arcas>
References: <JIRA.12634353.1361937807252@arcas>
Subject: [jira] [Updated] (HDFS-4534) Update rename for snapshots
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE updated HDFS-4534:
-----------------------------------------

    Attachment: h4534_20130314.patch

h4534_20130314.patch: also updates delete when the inode is a reference.

Since the patch is getting big, I intent to have the following task in a separate JIRA:
- change fsimage to handle reference;
- add rename tests.
                
> Update rename for snapshots
> ---------------------------
>
>                 Key: HDFS-4534
>                 URL: https://issues.apache.org/jira/browse/HDFS-4534
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: h4534_20130307.patch, h4534_20130313.patch, h4534_20130314.patch
>
>
> With rename, an inode may be moved from one location to another location in the namespace tree.  We need to take care the case that the inode is also in some snapshots.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira