[
https://issues.apache.org/jira/browse/HDFS-11679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013459#comment-16013459
]
Yuanbo Liu commented on HDFS-11679:
-----------------------------------
Before I provide a patch for this JIRA, I's propose to get rid of the option
{{-end}}
There are two cases while users use such kind of command {{hdfs scm -container
list -start <name> -end <name>}}:
* The end container name should be in the same datanode with start container
name, otherwise users cannot get the list in current architecture.
* The users needs to know that the end container is actually behind of the
start container, otherwise it returns nothing. It's hard for users to notice
the order ozone stores container names.
[~cheersyang] [~anu] What's your thoughts about this JIRA?
> 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
>
> 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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
