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 for this functionality.". How did you come to that conclusion? I'm aware of multiple ClientQuotaCallback implementations that rely on that method. Otherwise why would you also open KIP-1162, these 2 KIPs contradict each other! I don't want to vote for a feature to be deprecated and eventually removed without a clear plan for its users. Thanks, Mickael On Fri, Sep 12, 2025 at 2:03 AM Chia-Ping Tsai <[email protected]> wrote: > > 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 refer to the KIP: > > https://cwiki.apache.org/confluence/x/axBJFg > > > > Thanks! > > > > Best regards, > > Kuan-Po Tseng > >
