[jira] [Updated] (HDFS-11679) Ozone: SCM CLI: Implement list container command

["Yuanbo Liu (JIRA)" <ji...@apache.org>]

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

Yuanbo Liu updated HDFS-11679:
------------------------------
    Attachment: HDFS-11679-HDFS-7240.004.patch

[~cheersyang] / [~vagarychen]
Thanks for your comments.
1. Agree to make -start and -count as required. And it will solve the issues that you both mentioned above.
2.
{quote}
Also if we list on an empty db
{quote}
Addressed

3. the output is converted to JSON format:
{code}
{"containerName":"ContainerForTesting00","leaderHost":"127.0.0.1","datanodeHosts":["127.0.0.1"]}
{"containerName":"ContainerForTesting01","leaderHost":"127.0.0.1","datanodeHosts":["127.0.0.1"]}
...
{code}

> Ozone: SCM CLI: Implement list container command
> ------------------------------------------------
>
>                 Key: HDFS-11679
>                 URL: https://issues.apache.org/jira/browse/HDFS-11679
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Weiwei Yang
>            Assignee: Yuanbo Liu
>              Labels: command-line
>         Attachments: HDFS-11679-HDFS-7240.001.patch, HDFS-11679-HDFS-7240.002.patch, HDFS-11679-HDFS-7240.003.patch, HDFS-11679-HDFS-7240.004.patch
>
>
> Implement the command to list containers
> {code}
> hdfs scm -container list -start <container name> [-count <100> | -end <name>]{code}
> Lists all containers known to SCM. The option -start allows the listing to start from a specified container and -count controls the number of entries returned but it is mutually exclusive with the -end option which returns keys from the -start to -end range.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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