[
https://issues.apache.org/jira/browse/HDFS-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976721#comment-13976721
]
Daryn Sharp commented on HDFS-6266:
-----------------------------------
I'm only moderately familiar with snapshot handling, but how is a deleted file
inode that belongs to multiple snapshots handled? Ie. which snapshot will it
appear to belong to?
Is the need for this patch due to loss of the original array of inodes found
during path resolution?
> Identify full path for a given INode
> ------------------------------------
>
> Key: HDFS-6266
> URL: https://issues.apache.org/jira/browse/HDFS-6266
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-6266.000.patch
>
>
> Currently when identifying the full path of a given inode,
> FSDirectory#getPathComponents and FSDirectory#getFullPathName can only handle
> normal cases where the inode and its ancestors are not in any snapshot. This
> jira aims to provide support to handle snapshots. This can be useful for
> identifying the "Rename" change in a snapshot diff report.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
