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

Reply via email to