[GitHub] [pulsar] aloyszhang commented on a change in pull request #14655: Support delete schema forcefully

[GitBox <gi...@apache.org>]

aloyszhang commented on a change in pull request #14655:
URL: https://github.com/apache/pulsar/pull/14655#discussion_r825290898



##########
File path: pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdSchemas.java
##########
@@ -78,10 +78,14 @@ void run() throws Exception {
         @Parameter(description = "persistent://tenant/namespace/topic", required = true)
         private java.util.List<String> params;
 
+        @Parameter(names = { "-f",

Review comment:
       > From a user's perspective, when should they delete schema forcefully?
   
   A case I have met is all replicas of the ledger corresponding to the schema of the health-check topic were deleted (during the offline process of bookies), resulting in the failure of health-check and the failure is unrecoverable(can't update or delete the schema). I think the common topics also have the same problem.
   
   > Can we delete all schema forcefully?
   
   Do you mean all schemas for all topics? No, we can't




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org