> I'm aware of multiple ClientQuotaCallback implementations that rely on
that method.
I'm curious about that too. As Kuan-Po mentioned, the method was completely
unimplemented in KRaft mode until 4.0, which implies that is was not used
by KRraf users.
If there are users who avoided KRaft because
Hi Michael,
> No alternative method will be introduced, as there is currently no known
demand
> for this functionality.
Perhaps “no demand” was too strong a wording — apologies for that.
The real issue is that in 4.0 we reintroduced
ClientQuotaCallback#updateClusterMetadata(Cluster cluster) for K
Hi,
We have KIP-1162 to rethink ClientQuotaCallback. I think it would make
sense to handle the deprecation of older APIs in that KIP.
I'm not sure I understand why we have a separate KIP (this KIP).
The KIP states "No alternative method will be introduced, as there is
currently no known demand fo
hi kuan-po
the KIP looks good to me. Do you plan to start the vote thread?
Best,
Chia-Ping
On 2025/07/30 16:17:46 Kuan-Po Tseng wrote:
> Hi folks,
>
> I'd like to start a discussion thread about deprecating
> ClientQuotaCallback#updateClusterMetadata.
>
> For more context and details, please r
Hi folks,
I'd like to start a discussion thread about deprecating
ClientQuotaCallback#updateClusterMetadata.
For more context and details, please refer to the KIP:
https://cwiki.apache.org/confluence/x/axBJFg
Thanks!
Best regards,
Kuan-Po Tseng
