hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinayakumar B (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDFS-11061) Fix dfs -count -t or update its documentation
Date Thu, 27 Oct 2016 07:29:58 GMT

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

Vinayakumar B edited comment on HDFS-11061 at 10/27/16 7:29 AM:
----------------------------------------------------------------

{code}

         + "If a comma-separated list of storage types is given after the -t option, \n"
         + "it displays the quota and usage for the specified types. \n"
         + "Otherwise, it displays the quota and usage for all the storage \n"
-        + "types that support quota \n"
+        + "types that support quota. The list of possible storage "
+        + "types(case insensitive):\n"
+        + "empty string, all, ram_disk, ssd, disk and archive.\n"
{code}
Empty string, is nothing but, only "-t" switch is given, but not any values after that. The
result is same as 'all' passed as value for -t. So, this can be mentioned explicitly. But,
'empty string' and 'all' are not storagetypes. i.e. when 'all' cannot be combined with storagetypes.
But actual storagetypes can be comma separated multiple values.
I think this sentence can be corrected more.



was (Author: vinayrpet):
{quote}

         + "If a comma-separated list of storage types is given after the -t option, \n"
         + "it displays the quota and usage for the specified types. \n"
         + "Otherwise, it displays the quota and usage for all the storage \n"
-        + "types that support quota \n"
+        + "types that support quota. The list of possible storage "
+        + "types(case insensitive):\n"
+        + "empty string, all, ram_disk, ssd, disk and archive.\n"
{quote}
Empty string, is nothing but, only "-t" switch is given, but not any values after that. The
result is same as 'all' passed as value for -t. So, this can be mentioned explicitly. But,
'empty string' and 'all' are not storagetypes. i.e. when 'all' cannot be combined with storagetypes.
But actual storagetypes can be comma separated multiple values.
I think this sentence can be corrected more.


> Fix dfs -count -t or update its documentation
> ---------------------------------------------
>
>                 Key: HDFS-11061
>                 URL: https://issues.apache.org/jira/browse/HDFS-11061
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fs
>            Reporter: Wei-Chiu Chuang
>            Assignee: Yiqun Lin
>            Priority: Minor
>              Labels: supportability
>         Attachments: HDFS-11061.001.patch, HDFS-11061.002.patch
>
>
> According to dfs -count command line help, -t option must be used along with -q.
> * However, the current behavior is that  -t can be used without -q, it's just silently
ignored. 
> * In addition, -t may also be used with -u. 
> * The FileSystemShell doc does not state -t must be used along with -q. This should either
be enforced in the code, or update the doc/command line.
> * Also, the list of possible parameters for -t option is not described in the doc. Looking
at the code (Count.java), the list of possible parameters are either empty string (="all"),
"all", "ram_disk", "ssd", "disk" or "archive" (caseless)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message