[
https://issues.apache.org/jira/browse/HDFS-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980379#comment-13980379
]
Hadoop QA commented on HDFS-6266:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12641769/HDFS-6266.001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.datanode.TestBPOfferService
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6723//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6723//console
This message is automatically generated.
> Identify full path for a given INode
> ------------------------------------
>
> Key: HDFS-6266
> URL: https://issues.apache.org/jira/browse/HDFS-6266
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: snapshots
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-6266.000.patch, HDFS-6266.001.patch
>
>
> Currently when identifying the full path of a given inode,
> FSDirectory#getPathComponents and FSDirectory#getFullPathName can only handle
> normal cases where the inode and its ancestors are not in any snapshot. This
> jira aims to provide support to handle snapshots. This can be useful for
> identifying the "Rename" change in a snapshot diff report.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
