Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 14 Nov 2012 00:20:12 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <2001900623.111133.1352852412610.JavaMail.jiratomcat@arcas>
In-Reply-To: <1397646503.90027.1352429053057.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HDFS-4170) Add snapshot information to
 INodesInPath
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers commented on HDFS-4170:
--------------------------------------

bq. Yes, a snapshot path is supposed to be a path under an already-created snapshot, e.g. /foo/.snapshot/s1/bar. However, it also includes non-existing snapshots since paths may be provided by users. They could pass paths containing non-existing snapshots.

Got it, makes sense. Might want to make it clear in the comment then how that case could occur, and also clearly define "snapshot path" and "non-snapshot path."
                
> Add snapshot information to INodesInPath
> ----------------------------------------
>
>                 Key: HDFS-4170
>                 URL: https://issues.apache.org/jira/browse/HDFS-4170
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: Snapshot (HDFS-2802)
>
>         Attachments: h4170_20121108.patch, h4170_20121109.patch
>
>
> For snapshot paths, the snapshot information is required for accessing the snapshot.
> For non-snapshot paths, the latest snapshot found in the path is required for maintaining diffs for modification.

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