hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2219) Fsck should work with fully qualified file paths.
Date Wed, 14 Jan 2015 19:45:35 GMT

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

Hudson commented on HDFS-2219:

FAILURE: Integrated in Hadoop-trunk-Commit #6861 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6861/])
HDFS-2219. Change fsck to support fully qualified paths so that a particular namenode in a
federated cluster with multiple namenodes can be specified in the path parameter. (szetszwo:
rev 7fe0f25ad21f006eb41b832a181eb2a812a6f7b7)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSck.java
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsckWithMultipleNameNodes.java

> 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
>             Fix For: 2.7.0
>         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

View raw message