[
https://issues.apache.org/jira/browse/KAFKA-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847291#comment-16847291
]
ASF GitHub Bot commented on KAFKA-8422:
---------------------------------------
hachikuji commented on pull request #6806: KAFKA-8422; Client should send
OffsetForLeaderEpoch only if broker supports latest version
URL: https://github.com/apache/kafka/pull/6806
In the olden days, OffsetForLeaderEpoch was exclusively an inter-broker
protocol and required Cluster level permission. With KIP-320, clients can use
this API as well and so we lowered the required permission to Topic Describe.
The only way the client can be sure that the new permissions are in use is to
require version 3 of the protocol which was bumped for 2.3. If the broker does
not support this version, we skip the validation and revert to the old behavior.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Client should not use old versions of OffsetsForLeaderEpoch
> -----------------------------------------------------------
>
> Key: KAFKA-8422
> URL: https://issues.apache.org/jira/browse/KAFKA-8422
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Blocker
> Fix For: 2.3.0
>
>
> For KIP-320, we changed the permissions of the OffsetsForLeaderEpoch to be
> topic-level so that consumers did not require Cluster permission. However,
> there is no way for a consumer to know whether the broker is new enough to
> support this permission scheme. The only way to be sure is to use the version
> of this API that was bumped in 2.3. For older versions, we should revert to
> the old behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
