Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7713BDBDA for ; Tue, 19 Mar 2013 08:35:19 +0000 (UTC) Received: (qmail 22364 invoked by uid 500); 19 Mar 2013 08:35:17 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 22143 invoked by uid 500); 19 Mar 2013 08:35:17 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 21705 invoked by uid 99); 19 Mar 2013 08:35:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 08:35:16 +0000 Date: Tue, 19 Mar 2013 08:35:15 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-4612) Not to use INode.getParent() when generating snapshot diff report MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tsz Wo (Nicholas), SZE created HDFS-4612: -------------------------------------------- Summary: Not to use INode.getParent() when generating snapshot diff report Key: HDFS-4612 URL: https://issues.apache.org/jira/browse/HDFS-4612 Project: Hadoop HDFS Issue Type: Sub-task Components: namenode Reporter: Tsz Wo (Nicholas), SZE Assignee: Tsz Wo (Nicholas), SZE With rename, an inode may have multiple access paths, i.e. multiple parents. In such case, INode.getParent() returns the parent in the current state but not the parents in the snapshots. Therefore, we cannot use INode.getParent() to generate snapshot diff report. -- 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