-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
KIP-546 Client quota APIs #1909
Conversation
@agriffaut thanks for your contribution, this is great! One question I had after an initial scan over the PR, was there a design goal around consistently using slices of pointers in the protocol definitions here? The slices will always either be empty or filled and will never have |
I rebased and it also looks like
|
@agriffaut 👋 any thoughts on the above comments? |
@dnwe I finally managed to work again on that PR, sorry for the delay. Please tell me if this looks good to you! |
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
Thanks for your contribution @agriffaut. I'll wait for |
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. Thanks again for the PR and the updates 🙇
Thanks @dnwe for reviewing 🙏🏼 |
This PR implements the new ClientQuota API, available since Kafka 2.6.0.0
KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-546%3A+Add+Client+Quota+APIs+to+the+Admin+Client
Protocols:
https://kafka.apache.org/protocol#The_Messages_DescribeClientQuotas
https://kafka.apache.org/protocol#The_Messages_AlterClientQuotas