[
https://issues.apache.org/jira/browse/HDFS-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613293#comment-13613293
]
Suresh Srinivas commented on HDFS-4489:
---------------------------------------
bq. all the patches make sense to me, it's just that several of them don't
really stand on their own
I am not sure I understand this. One of the main reasons for a feature branch
(at least for me), while during development, we may break trunk. But in this
case that is not the case.
I have cleaned up the list of subtasks in this jira. Hopefully the subtasks
should make it more clear.
Let me add some details about individual jiras and that should help in
understanding them better:
# HDFS-4334 - Adds unique ID to each INode.
# HDFS-4346 - Refactored the code to remove code duplication between INode
generation and block ID generation
# HDFS-4339 - Persist the INode in fsimage.
# HDFS-4434 - Introduce a map of inode ID to inode so that inodeid/fileid can
be used as an identifier to address a file
> Use InodeID as as an identifier of a file in HDFS protocols and APIs
> --------------------------------------------------------------------
>
> Key: HDFS-4489
> URL: https://issues.apache.org/jira/browse/HDFS-4489
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Brandon Li
> Assignee: Brandon Li
>
> The benefit of using InodeID to uniquely identify a file can be multiple
> folds. Here are a few of them:
> 1. uniquely identify a file cross rename, related JIRAs include HDFS-4258,
> HDFS-4437.
> 2. modification checks in tools like distcp. Since a file could have been
> replaced or renamed to, the file name and size combination is no t reliable,
> but the combination of file id and size is unique.
> 3. id based protocol support (e.g., NFS)
> 4. to make the pluggable block placement policy use fileid instead of
> filename (HDFS-385).
--
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
