Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove residual info after forcibly deleting the namespace #10465

Merged
merged 1 commit into from
May 3, 2021

Conversation

315157973
Copy link
Contributor

@315157973 315157973 commented May 2, 2021

Motivation

Forcibly deleting the namespace will leave a large number of schemas.
Topic and namespace are deleted, leaving the schema is meaningless.
If both Topic and namespace are deleted, we cannot find the schemas that need to be deleted based on other info

Modifications

When the namespace is forcibly deleted, the schema is also deleted

Verifying this change

@codelipenghui codelipenghui added this to the 2.8.0 milestone May 3, 2021
@codelipenghui codelipenghui merged commit 2cf9070 into apache:master May 3, 2021
@315157973 315157973 deleted the deleteNamespace branch May 11, 2021 09:02
eolivelli pushed a commit to eolivelli/pulsar that referenced this pull request May 11, 2021
)

### Motivation
Forcibly deleting the namespace will leave a large number of schemas. 
Topic and namespace are deleted, leaving the schema is meaningless.
If both Topic and namespace are deleted, we cannot find the schemas that need to be deleted based on other info

### Modifications
When the namespace is forcibly deleted, the schema is also deleted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants