[
https://issues.apache.org/jira/browse/KAFKA-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346423#comment-17346423
]
A. Sophie Blee-Goldman commented on KAFKA-12781:
------------------------------------------------
Ah, that's my bad – I was discussing this with Walker since I had also
misunderstood the meaning of the current endOffsets() API, and recommended that
he use the new API from John's KIP but then took it back as I thought we had
reverted the new API in that task idling KIP. But I guess we only reverted some
of the changes, of course we would still have required the currentLag().
In that case I agree with Guozhang, we can just knock this out right away with
a small PR to leverage the currentLag() API. I'm putting the fix version as 3.0
since it may not be critical to address this ASAP, but since it's an easy fix
we should get to it by the time this is released. That will also help with the
confusion around what endOffsets() means, since if both Guozhang and I
misunderstood it then I'm guessing some users will too.
> Improve the endOffsets accuracy in TaskMetadata
> ------------------------------------------------
>
> Key: KAFKA-12781
> URL: https://issues.apache.org/jira/browse/KAFKA-12781
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 2.8.0
> Reporter: Walker Carlson
> Priority: Minor
>
> Currently `TaskMetadata#endOffsets()` returns the highest offset seen by the
> main consumer in streams. It should be possible to get the highest offset in
> the topic via the consumer instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
