lucasbru commented on PR #23855: URL: https://github.com/apache/kafka/pull/23855#issuecomment-6291430425
Small addition after looking at how the client builds the groups: the order comes from `HashSet` iteration in `InternalTopologyBuilder#copartitionGroups`, which is deterministic for the same topology code. So instances running the same code always send the same order, and the mismatch only happens when equivalent topologies are written differently (e.g. join order swapped) and the topic names collide in the same hash bucket. That also means existing records generally match what current clients send, which makes your point about sorting on the client even stronger. A sorting client would usually differ from the persisted order on an unpatched broker. -- 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]
