hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5988) Add a command to ' FsShell stat ' to get a file's block location information
Date Mon, 27 Jul 2009 09:03:14 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735534#action_12735534

Edward J. Yoon commented on HADOOP-5988:

Thanks for your review. I'll check them.

>> For more eaier to read, i think the output should be indented (especially the byte
range part), what do you think? 

And, I agree with you. Below is the output of the '# bin/hadoop fs -stat %B tmp/src.tar.gz'.

09/07/27 17:50:01 WARN conf.Configuration: DEPRECATED: hadoop-site.xml found in the classpath.
Usage of hadoop-site.xml is deprecated. Instead use core-site.xml, mapred-site.xml and hdfs-site.xml
to override properties of core-default.xml, mapred-default.xml and hdfs-default.xml respectively
byte-range:0-67108864   location:dev1.nm;
byte-range:67108864-134217728   location:dev1.nm;
byte-range:134217728-201326592  location:dev1.nm;
byte-range:201326592-268435456  location:dev1.nm;
byte-range:268435456-335544320  location:dev1.nm;
byte-range:335544320-402653184  location:dev1.nm;
byte-range:402653184-469762048  location:dev1.nm;
byte-range:469762048-517866001  location:dev1.nm;

> Add a command to ' FsShell stat ' to get a file's block location information
> ----------------------------------------------------------------------------
>                 Key: HADOOP-5988
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5988
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: He Yongqiang
>         Attachments: HADOOP-5988.patch
> Adding an option to ' FsShell stat ' to get a file's block location information will
be very useful.
> we can print the block location information in this format:
> blockID:XXXXX  byte-range:YYYY-ZZZZ  location:dn1;dn2;
> blockID:XXXXX  byte-range:YYYY-ZZZZ  location:dn1;dn2;

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message