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

Hadoop QA commented on HDFS-11675:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  8s{color} 
| {color:red} HDFS-11675 does not apply to HDFS-7240. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-11675 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12865398/HDFS-11675-HDFS-7240.001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/19219/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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: HDFS-11675-HDFS-7240.001.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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to