Hi Shekhar Rajak, I think that the overall direction looks pretty good. Some of the details about how the Kafka protocol would evolve are missing, so I've written a wiki page with my initial thoughts (https://cwiki.apache.org/confluence/spaces/KAFKA/pages/446071036/Design+notes). I also tried to simplify the application programming interface.
Let me know what you think. Thanks, Andrew On 2026/08/04 13:26:37 Andrew Schofield wrote: > Hi, > Thanks for the comprehensive updates to the KIP and the supporting document. > This is a great help for me to review the proposal. I will spend some time > this week reviewing it in depth and providing feedback. > > Thanks, > Andrew > > On 2026/08/03 17:00:05 Shekhar Prasad Rajak via dev wrote: > > Hi team, > > I’ve spent the last few months diving deep into our share group mechanics, > > specifically focusing on distributed acknowledgements, fault tolerance, and > > recovery protocols. To move us forward, I’ve mapped out a detailed design > > and architectural diagrams here: > > https://docs.google.com/document/d/1sWMZ1c3j_rwg1jQByZ4rW-66GGoswkRI3DnSUiJPJ94/edit?tab=t.0 > > > > > > Public APIs and High level overview KIP: > > https://cwiki.apache.org/confluence/x/J448G > > Please review the proposals so we can align on the implementation details. > > Next, I will outline the integration plan with Flink to support queue > > semantics (as a proof that our KIP changes will going to help stream > > processing engines like Flink) where consumer elasticity matters more than > > throughput, and topics with severe partition skew. > > Regards,Shekhar Rajak >
