[
https://issues.apache.org/jira/browse/KAFKA-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668262#comment-16668262
]
ASF GitHub Bot commented on KAFKA-7568:
---------------------------------------
hachikuji opened a new pull request #5855: KAFKA-7568; Return leader epoch in
ListOffsets response
URL: https://github.com/apache/kafka/pull/5855
As part of KIP-320, the ListOffsets API should return the leader epoch of
any fetched offset. We either get this epoch from the log itself for a
timestamp query or from the epoch cache if we are searching the earliest or
latest offset in the log. When handling queries for the latest offset, we have
elected to choose the current leader epoch, which is consistent with other
handling (e.g. OffsetsForTimes).
### 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 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
> Return leader epoch in ListOffsets responses
> --------------------------------------------
>
> Key: KAFKA-7568
> URL: https://issues.apache.org/jira/browse/KAFKA-7568
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> This is part of KIP-320. The changes to the API have already been made, but
> currently we return unknown epoch. We need to update the logic to search for
> the epoch corresponding to a fetched offset in the leader epoch cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
