[
https://issues.apache.org/jira/browse/HDFS-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-6266:
----------------------------
Attachment: HDFS-6266.000.patch
Initial patch. The patch handles two scenarios:
1. The given inode is contained in a snapshot (i.e., the inode or one of its
ancestors has been deleted but is currently stored in a snapshot). For handling
this scenario, we have to check whether the inode (and its ancestor) is in the
children list of its parent or in the deleted list of a snapshot diff.
2. The given inode or one of its ancestors have been renamed within or across
snapshottable directories.
In general, to handling snapshots while identifying full path requires extra
checking on snapshot diff information. A suitable use case may be calculating
the snapshot diff report or debugging snapshot code. We should still use the
original getFullPathName when processing inodes in the current fsdirectory tree.
> 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)
