[
https://issues.apache.org/jira/browse/KAFKA-17093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863689#comment-17863689
]
Tom Kalmijn commented on KAFKA-17093:
-------------------------------------
kangning, thank you so much for your time and effort! I do apologise if my
issue makes you double things which are actually ok.
Maybe I am mistaken about the meaning of LSO. I understand "read_committed"
instructs a consumer to look at committed messages only. If so I find it
surprising that seekToEnd() takes me to an offset where there is nothing to be
read? I am after the offset of the last existing message in a partition. If
seekToEnd does not take me there then I have to resort to back tracking an
polling to figure out where this message is at?
> KafkaConsumer.seekToEnd should return LSO
> ------------------------------------------
>
> Key: KAFKA-17093
> URL: https://issues.apache.org/jira/browse/KAFKA-17093
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 3.6.1
> Environment: Ubuntu, IntelliJ, Scala "org.apache.kafka" %
> "kafka-clients" % "3.6.1"
> Reporter: Tom Kalmijn
> Priority: Major
>
>
> Expected
> When using a transactional producer then the method
> KafkaConsumer.seekToEnd(...) of a consumer configured with isolation level
> "read_committed" should return the LSO.
> Observed
> The offset returned is always the actual last offset of the partition, which
> is not the LSO if the latest offsets are occupied by transaction markers.
> Also see this Slack thread:
> https://confluentcommunity.slack.com/archives/C499EFQS0/p1720088282557559
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
