-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[Issue 7959] Added support to force deleting namespace #7993
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
Merged
+374
−20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix a unit test
b24f3e3
to
9a3905a
Compare
/pulsarbot run-failure-checks |
@BewareMyPower to also take a look |
/pulsarbot run-failure-checks |
jiazhai
approved these changes
Sep 21, 2020
BewareMyPower
pushed a commit
to streamnative/pulsar-archived
that referenced
this pull request
Oct 1, 2020
### Motivation Fixes apache#7959 ### Modifications Add a optional field to force the deletion of all stuffs related to namespace.
lbenc135
pushed a commit
to lbenc135/pulsar
that referenced
this pull request
Oct 3, 2020
### Motivation Fixes apache#7959 ### Modifications Add a optional field to force the deletion of all stuffs related to namespace.
wolfstudy
pushed a commit
that referenced
this pull request
Oct 30, 2020
sijie
pushed a commit
that referenced
this pull request
Dec 4, 2020
…#8806) ### Motivation We found a issue that when force deleting a namespace, only topics owned by the broker were deleted, topics owned by other brokers were not deleted. The force delete namespace feature was added in #7993 . ### Modifications Use admin client to delete the topic, which could delete all topics include those owned by other brokers.
codelipenghui
pushed a commit
that referenced
this pull request
Dec 7, 2020
…#8806) ### Motivation We found a issue that when force deleting a namespace, only topics owned by the broker were deleted, topics owned by other brokers were not deleted. The force delete namespace feature was added in #7993 . ### Modifications Use admin client to delete the topic, which could delete all topics include those owned by other brokers. (cherry picked from commit 75af6c2)
RobertIndie
pushed a commit
to RobertIndie/pulsar
that referenced
this pull request
Dec 8, 2020
…apache#8806) ### Motivation We found a issue that when force deleting a namespace, only topics owned by the broker were deleted, topics owned by other brokers were not deleted. The force delete namespace feature was added in apache#7993 . ### Modifications Use admin client to delete the topic, which could delete all topics include those owned by other brokers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Fixes #7959
Modifications
Add a optional field to force the deletion of all stuffs related to namespace.