[
https://issues.apache.org/jira/browse/KAFKA-18225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18225.
------------------------------------
Resolution: Fixed
trunk:
https://github.com/apache/kafka/commit/70adf746c472f9136a6e7b7bc61a2b79a4117198
4.0:
https://github.com/apache/kafka/commit/ad6db0952bc12577d08c1e1471d1fd473f43acca
> ClientQuotaCallback#updateClusterMetadata is unsupported by kraft
> -----------------------------------------------------------------
>
> Key: KAFKA-18225
> URL: https://issues.apache.org/jira/browse/KAFKA-18225
> Project: Kafka
> Issue Type: Task
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Blocker
> Fix For: 4.0.0
>
>
> `ClientQuotaCallback#updateClusterMetadata` is invoked by
> `KafkaAPIs#handleUpdateMetadataRequest` only. However, that is a zk-only API
> and hence, `updateClusterMetadata` is never executed in kraft mode. That
> brings two issues:
> 1. CustomQuotaCallbackTest needs to be rewritten hugely in order to migrate
> to kraft
> 2. Should we deprecate `updateClusterMetadata` directly in 4.0? or make it
> work on kraft mode or introduce new API to replace it
> Regardless to '2', we can enhance `DynamicClientQuotaPublisher` to support
> `ClientQuotaCallback#updateClusterMetadata` when handling `newImage`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
