[ 
https://issues.apache.org/jira/browse/HDFS-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275690#comment-14275690
 ] 

Hadoop QA commented on HDFS-2219:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12691953/h2219_20150113.patch
  against trunk revision 08ac062.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 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 2.0.3) 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 following test timeouts occurred in 
hadoop-hdfs-project/hadoop-hdfs:

org.apache.hadoop.hdfs.server.blockmanagement.TestDatanodeManager

Test results: 
https://builds.apache.org/job/PreCommit-HDFS-Build/9197//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9197//console

This message is automatically generated.

> Fsck should work with fully qualified file paths.
> -------------------------------------------------
>
>                 Key: HDFS-2219
>                 URL: https://issues.apache.org/jira/browse/HDFS-2219
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: tools
>    Affects Versions: 0.23.0
>            Reporter: Jitendra Nath Pandey
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Minor
>         Attachments: h2219_20150113.patch
>
>
> Fsck takes absolute paths, but doesn't work with fully qualified file path 
> URIs. In a federated cluster with multiple namenodes, it will be useful to be 
> able to specify a file path for any namenode using its fully qualified path. 
> Currently, a non-default file system can be specified using -fs option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to