[
https://issues.apache.org/jira/browse/HDFS-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642118#comment-13642118
]
Konstantin Shvachko commented on HDFS-4489:
-------------------------------------------
Posted a request for the bases for porting this to branch 2.0.5 in HDFS-4434.
suresh> What is the concern?
My concern is that you committed incompatible change, which is a new feature
and a large change, into the stabilization branch without a vote or a release
plan discussed with the community.
Being a bad practice in general, I think it is a wrong move now in particular,
because people are discussing the stabilization of 2.0.5.
This feature totals about 150K of code in patches (counting subtasks only). Not
helping stabilization. And you didn't give any reasons for the merge.
I would like to ask to revert this merge from branch 2.0.5 and follow the
procedures for merging features into new release branches if you decide to
proceed.
> 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
