Hi Josep, Thanks for the proposed KIP. It looks good to me overall. One meta comment is that in order to illustrate whether that fits more cleanly to the actual metadata use cases, we could add a few examples each with its code snippet based on the new APIs. The ones I'm having in mind are:
1) Give me the list of hosts for a specific store, and let me know who is the active host and who are the standbys. 2) Give me the list of hosts for a specific store and a specific key of the store, and let me know who is the active host and who are the standbys. 3) Give me all the embedded client ids of the current instance, across all of its threads. 4) Let me know how many threads the instance has, and their current status. 5) Let me know for a given store, how far in terms of records is each of the standbys lagging behind the active replica. Guozhang On Fri, Dec 3, 2021 at 11:15 AM Josep Prat <[email protected]> wrote: > Hi all, > > I've created KIP-807 to refactor KafaStreams exposed metadata hierarchy. > Here you can find the document: > https://cwiki.apache.org/confluence/x/TpiqCw > > Please take a look at the proposal and let me know what you think, > > Thanks in advance, > > -- > > Josep Prat > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491715557497 > > *w:* aiven.io > > *e:* [email protected] > -- -- Guozhang
