> > > I don't see how it helps. If the client is communicating with a broker that > does not support KIP-35, that broker will simply close the connection. If > the broker supports KIP-35, then it will provide the broker version. I > don't envisage a scenario where a broker does not support KIP-35, but > implements the new behaviour of sending an empty response. Do you? > > Are you sure about that? Per KIP-35, the broker supplies the version in response to Metadata request, not in response to anything else. If the client sends producer request version 42 (accidentally or due to premature upgrade) to KIP-35-compactible broker - we want to see an empty packet and not a connection close. Sending a broker version was deemed impractical IIRC.
> Ismael >
