[ https://issues.apache.org/jira/browse/HDFS-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642355#comment-13642355 ]
Konstantin Shvachko commented on HDFS-4489: ------------------------------------------- Suresh whatever reason for incompatibility it should go through approval process. You also committed the LayoutVersion change HDFS-4296. Now it requires an upgrade. > one of the goal for 2.0.5 is drive towards a state where incompatible changes > are not allowed after it. That was the goal for Hadoop 0.20. I thought the goal for 2.0.5 is stabilization. > Also merging to branch-2 in a lot of cases is done based on a committer's > judgement. I think it is wrong. Especially for the stabilization release. > I think there is enough motivation for the feature posted in the jira. Not arguing about the value of the feature. But about its necessity for 2.0.5 > Is your concern about HDFS-4434 or all the related changes? Most of them. I would have reviewed if I had a proper warning. So again why is it necessary for 2.0.5? > 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