You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Konstantine Karantasis (Jira)" <ji...@apache.org> on 2021/07/09 03:24:00 UTC
[jira] [Commented] (KAFKA-12781) Improve the endOffsets accuracy in
TaskMetadata
[ https://issues.apache.org/jira/browse/KAFKA-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377752#comment-17377752 ]
Konstantine Karantasis commented on KAFKA-12781:
------------------------------------------------
[~ableegoldman] [~wcarlson5] we have passed feature freeze for 3.0 and this issue doesn't seem to be a bug. Postponing to the subsequent release.
[|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13377582]
> 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
> Reporter: Walker Carlson
> Priority: Minor
> Fix For: 3.0.0
>
>
> 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)