[
https://issues.apache.org/jira/browse/HDFS-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643424#comment-13643424
]
Suresh Srinivas commented on HDFS-4489:
---------------------------------------
bq. There is still an incompatible change HDFS-4296. It is listed in new
features for some reason.
It is not incompatible and hence not marked as incompatible in jira or
CHANGES.txt. It is currently listed as New Feature in CHANGES.txt. I do not
think it should be listed under New Features section (though it does not
qualify for Improvement, Bug fix any of that). I will move it to bug fix
section.
bq. Do you still need HDFS-4296 once HDFS-434 is reverted?
It is needed because it corresponds to a layout version reserved in branch-1
for concat. It is not related to HDFS-4434.
> 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
> Fix For: 2.0.5-beta
>
>
> 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
