chickenchickenlove commented on PR #23855: URL: https://github.com/apache/kafka/pull/23855#issuecomment-6290562779
@lucasbru Thanks for taking the time to review! I agree that we should fix the client side as well. Given the backport implications, would it make sense to track that change in a separate ticket and PR? AFAIK, Copartition groups are persisted, including their ordering. If an existing client is upgraded to send sorted groups while the broker remains unpatched, the broker could reject the topology because its ordering differs from the persisted record, even though the topology is semantically unchanged. Separating the client-side change would let us backport the broker normalization independently and evaluate the client-side backport with this compatibility concern in mind. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
