-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[fix][broker]fix catching ConflictException when update topic partition #17374
Conversation
Good catch! Please follow the PR naming standard. https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit#heading=h.wu6ygjne8e35 |
Nice catch. The code below hide the exception, that's why the test can pass without throw exception. I think the code below wants to try to solve the same problem as #17251, but has some problem. I think that we can also remove the code from Line4399-Line4402. Because #17251 fix it better. WDYT @TakaHiR07 pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/PersistentTopicsBase.java Lines 4398 to 4405 in dab0d1f
|
@AnonHxy I think it is good! We do not need this code after #17251. I have force-push to contain this change. |
@Jason918 PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…on (apache#17374) Co-authored-by: fanjianye <[email protected]>
…on (#17374) Co-authored-by: fanjianye <[email protected]>
Motivation
A fix for #17251. There is an error when handling ConflictException.
The previous unittest can not approve it, so I add another test.
Modifications
ex.getCause() -> ex
add test.
Verifying this change
Documentation
Check the box below or label this PR directly.
Need to update docs?
doc-required
(Your PR needs to update docs and you will update later)
doc-not-needed
(Please explain why)
doc
(Your PR contains doc changes)
doc-complete
(Docs have been already added)