[
https://issues.apache.org/jira/browse/KAFKA-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849122#comment-16849122
]
ASF GitHub Bot commented on KAFKA-8437:
---------------------------------------
hachikuji commented on pull request #6823: KAFKA-8437; Await node api versions
before checking if offset validation is possible
URL: https://github.com/apache/kafka/pull/6823
The consumer should await api version information before determining whether
the broker supports offset validation. In KAFKA-8422, we skip the validation if
we don't have api version information, which means we always skip validation
the first time we connect to a node.
### 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
> Consumer should wait for api version before checking if offset validation is
> possible
> -------------------------------------------------------------------------------------
>
> Key: KAFKA-8437
> URL: https://issues.apache.org/jira/browse/KAFKA-8437
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> KAFKA-8422 fixed a problem with ACL assumptions made during offset
> validation. If using an old api version, we skip the validation. However, if
> we do not have an active connection to the node, then we will not have api
> version information available. Rather than skipping the validation check as
> we did in KAFKA-8422, we should await the version information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
