You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the protocol document, brokers are supposed to reject messages containing a higher API version than they understand. This is important because the encoded response does not contain the API version used.
Jocko declares to the client which API versions it supports (defined in protocol/api_versions.go). But I can't see whether it enforces this in incoming requests, and I think it should. It would just be a question of checking the received API version (second field in Request Header) against the min/max values in protocol.APIVersions
The text was updated successfully, but these errors were encountered:
According to the protocol document, brokers are supposed to reject messages containing a higher API version than they understand. This is important because the encoded response does not contain the API version used.
Jocko declares to the client which API versions it supports (defined in
protocol/api_versions.go
). But I can't see whether it enforces this in incoming requests, and I think it should. It would just be a question of checking the received API version (second field in Request Header) against the min/max values in protocol.APIVersionsThe text was updated successfully, but these errors were encountered: