[
https://issues.apache.org/jira/browse/HDFS-15319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157899#comment-17157899
]
Hudson commented on HDFS-15319:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18438 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/18438/])
HDFS-15319. Fix INode#isInLatestSnapshot() API. Contributed by (shashikant: rev
85d4718ed737d3bfadf815765336465a7a98bc47)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/INode.java
> Fix INode#isInLatestSnapshot() API
> ----------------------------------
>
> Key: HDFS-15319
> URL: https://issues.apache.org/jira/browse/HDFS-15319
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 3.0.4
>
> Attachments: HDFS-15319.000.patch, HDFS-15319.001.patch
>
>
> isInLatestSnapshot() may return true in cases where an inode's ancesstors
> might not be in the latest snapshot.
> {code:java}
> // if parent is a reference node, parent must be a renamed node. We can
> // stop the check at the reference node.
> if (parent != null && parent.isReference()) {
> // TODO: Is it a bug to return true?
> // Some ancestor nodes may not be in the latest snapshot.
> return true;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
