aloyszhang opened a new issue #14654: URL: https://github.com/apache/pulsar/issues/14654
**Is your enhancement request related to a problem? Please describe.** Currently, pulsar admin command for schemas can't delete a schema completely， it only appends a deleted `schemaInfo` to mark this schema as deleted. Internal, when deleting a schema, pulsar will first read the existing schemas append the deleted `schemaInfo` This design may have some problems: 1. Schema has a `SchemaLocator` in metastore that contains the ledgerId which we save the `SchemaInfo` in. If all the replica of the schema ledger is lost or broken, the schema can neither be recovered nor be deleted, leading to the clients(producers and consumers) failing. 2. Delete a topic without deleting schema, even we delete the schema after, there will be a useless `SchemaLocator` in metastore and a ledger in BookKeeper left. 3. Delete a schema for a topic(even the topic does not exist) will lefter a useless `SchemaLocator` in metastore and a ledger in BookKeeper **Describe the solution you'd like** We should support delete schema forcefully to make sure the `SchemaLocator` in metastore and ledger in BookKeeper can be cleaned completely. **Describe alternatives you've considered** None **Additional context** No -- 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-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
