[
https://issues.apache.org/jira/browse/KAFKA-10613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-10613.
-----------------------------------
Fix Version/s: 2.7.0
Resolution: Fixed
> Broker should not set leader epoch if the list-offset request version < 4
> -------------------------------------------------------------------------
>
> Key: KAFKA-10613
> URL: https://issues.apache.org/jira/browse/KAFKA-10613
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Priority: Major
> Fix For: 2.7.0
>
>
> The list-offset response added a new field in version 4:
> {code}
> { "name": "LeaderEpoch", "type": "int32", "versions": "4+" }
> {code}
> And the compiled code would throw UnsupportedVersionException if that field
> is not default (-1) with version < 4. However, on the broker side we forget
> to add the logic to not setting this field based on the request version. This
> would cause old versioned clients' list-offset call to always get
> UnsupportedVersionException and an empty result would be returned.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
