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

Weiwei Yang commented on HDFS-11675:
------------------------------------

Hi [~xyao]

Thanks, they did output these info in console. But you actually reminds me we 
should get rid of printing outputs in CLI via log4j, SCM CLI has the ability to 
set customized print streams (that is currently used in UT, and is useful in 
feature if we want to support a common option -f to redirect output to some 
files). I just uploaded v5 patch to remove {{LOG}} entries and replaced them 
with {{OzoneCommandHandler#logout()}} which prints outputs to certain print 
stream. Please let me know if it sounds good or not. Thank you.

> Ozone: SCM CLI: Implement delete container command
> --------------------------------------------------
>
>                 Key: HDFS-11675
>                 URL: https://issues.apache.org/jira/browse/HDFS-11675
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>              Labels: command-line
>         Attachments: Container_create_del_command_tests, 
> HDFS-11675-HDFS-7240.001.patch, HDFS-11675-HDFS-7240.002.patch, 
> HDFS-11675-HDFS-7240.003.patch, HDFS-11675-HDFS-7240.004.patch, 
> HDFS-11675-HDFS-7240.005.patch
>
>
> Implement delete container
> {code}
> hdfs scm -container del <container name> -f
> {code}
> Deletes a container if it is empty. The -f options can be used to force a 
> delete of a non-empty container. If container name specified not exist, 
> prints a clear error message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to