Hi Kuan Po Tseng, Thank you for starting this discussion. This would be a very nice improvement.
It seems that the current scheme requires everyone writing an implementation of ClientQuotaCallackHandler to implement the old updateClusterMetadata function that takes a Cluster. That seems less than ideal, since once we remove that deprecated function, it will break compilation for anyone implementing it. Should we instead have a new interface (which can inherit from the old interface, for now)? That would avoid this issue... best, Colin On Tue, Apr 22, 2025, at 09:23, Kuan Po Tseng wrote: > Hello everyone, > > I’d like to kick off a discussion about redesigning > ClientQuotaCallback#updateClusterMetadata. > As it stands, the current implementation is quite inefficient, since it > requires creating > a full Cluster object each time any change is made. On top of that, some of > the information > within the Cluster object is outdated. > > With that in mind, I’d love to propose a lighter, more efficient solution, > along with a redefined > interface for the object passed into updateClusterMetadata. If you have a > moment, I’d really appreciate your thoughts and feedback on this. > > Thank you! > > KIP link: https://cwiki.apache.org/confluence/x/zInoF > > Best, > Kuan-Po Tseng
