[
https://issues.apache.org/jira/browse/HDFS-11675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986993#comment-15986993
]
Weiwei Yang commented on HDFS-11675:
------------------------------------
Some notes for review
# Changes to {{ContainerCommandHandler}}, {{ContainerOperationClient}} and
{{DeleteContainerHandler}} are pretty nature, according to the CLI classes
based HDFS-11649.
# Implemented delete container in {{ContainerProtocolCalls}}.
# Implemented {{getContainer}} call, this is the 1st step to delete a container
because we need to know where the container is located. Related changes are in
{{StorageContainerLocationProtocol}} classes.
# {{TestSCMCli#testDeleteContainer}} tested empty container, non-empty
container and force delete on various of conditions.
# Other misc changes are to support the force flag, and expose some field for
testing only.
> 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]
