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

[fix][broker] fix can not revoke permission after update topic partition #17393

Merged
merged 2 commits into from Sep 5, 2022

Conversation

TakaHiR07
Copy link
Contributor

Motivation

related to #16768

Modifications

should not fail a request that attempts to remove permission from a partition of a topic that was not already granted permission

Verifying this change

  • Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

  • Dependencies (does it add or upgrade a dependency): no
  • The public API: no
  • The schema: no
  • The default values of configurations: no
  • The wire protocol: no
  • The rest endpoints: no
  • The admin cli options: no
  • Anything that affects deployment: no

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)

@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Sep 1, 2022
@TakaHiR07
Copy link
Contributor Author

This is the first PR only fix can not revoke permission problem. You can take a look. @michaeljmarshall @nodece

Copy link
Member

@michaeljmarshall michaeljmarshall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. This is a very clean solution.

@mattisonchao
Copy link
Member

@TakaHiR07
It looks like we got many conflicts when cherry-picking it to branch-2.9.
Would you mind pushing a PR to branch-2.9? (To avoid cherry-picking involving bugs)

@TakaHiR07
Copy link
Contributor Author

TakaHiR07 commented Sep 13, 2022

@TakaHiR07 It looks like we got many conflicts when cherry-picking it to branch-2.9. Would you mind pushing a PR to branch-2.9? (To avoid cherry-picking involving bugs)

@mattisonchao I can help cherry-pick the relevant 2 pr to branch-2.9.

congbobo184 pushed a commit that referenced this pull request Nov 14, 2022
@congbobo184 congbobo184 added the cherry-picked/branch-2.9 Archived: 2.9 is end of life label Nov 14, 2022
liangyepianzhou pushed a commit that referenced this pull request Dec 5, 2022
…ion (#17393)

* add unittest for revoke permission of topic after update topic partition

* fix revoke permission of partition

Co-authored-by: fanjianye <fanjianye@bigo.sg>
(cherry picked from commit 8c4aad5)
nicoloboschi pushed a commit to datastax/pulsar that referenced this pull request Dec 6, 2022
…ion (apache#17393)

* add unittest for revoke permission of topic after update topic partition

* fix revoke permission of partition

Co-authored-by: fanjianye <fanjianye@bigo.sg>
(cherry picked from commit 8c4aad5)
(cherry picked from commit 2d0190f)
congbobo184 pushed a commit that referenced this pull request Dec 7, 2022
### Motivation

cherry-pick #17393 to branch-2.9

(cherry picked from commit 863ea60)
Technoboy- pushed a commit that referenced this pull request Feb 8, 2023
…ion (#17393)

* add unittest for revoke permission of topic after update topic partition

* fix revoke permission of partition

Co-authored-by: fanjianye <fanjianye@bigo.sg>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants