[ 
https://issues.apache.org/jira/browse/HADOOP-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward J. Yoon updated HADOOP-5988:
-----------------------------------

    Attachment: HADOOP-5988_v01.patch

I just changed output like this.

{code}
[r...@udanax hadoop-common-trunk]# bin/hadoop fs -stat %B tmp/aa.tar
09/07/28 11:48:26 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:udanax.org;             |
+----------------------------------+
| byte-range:67108864-134217728    |
| location:udanax.org;             |
+----------------------------------+
 ..
+----------------------------------+
| byte-range:2147483648-2165155840 |
| location:udanax.org;             |
+----------------------------------+

[r...@udanax hadoop-common-trunk]# bin/hadoop fs -stat %B tmp/aa.ta
09/07/28 11:50:00 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
stat: cannot stat `tmp/aa.ta': No such file or directory
{code}

> 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, HADOOP-5988_v01.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.

Reply via email to