[
https://issues.apache.org/jira/browse/HDFS-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509656#comment-13509656
]
Hudson commented on HDFS-4243:
------------------------------
Integrated in Hadoop-Yarn-trunk #56 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/56/])
HDFS-4243. When replacing an INodeDirectory, the parent pointers of the
children of the child have to be updated to the new child. Contributed by Jing
Zhao (Revision 1416709)
Result = SUCCESS
szetszwo :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1416709
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogLoader.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/INodeDirectory.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestINodeFile.java
> INodeDirectory.replaceChild(..) does not update parent
> ------------------------------------------------------
>
> Key: HDFS-4243
> URL: https://issues.apache.org/jira/browse/HDFS-4243
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Jing Zhao
> Fix For: 3.0.0
>
> Attachments: HDFS-4243.001.patch, HDFS-4243.002.patch,
> HDFS-4243.003.patch
>
>
> The method replaces an existing child with a new child. However, it does not
> take care the case the child also an INodeDirectory. In such case, the
> parent pointers of the children of the child have to be updated to the new
> child.
> Only FSDirectory.unprotectedSetQuota(..) calls this method so that the child
> is always an INodeDirectory.
--
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
