You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/06/30 23:07:00 UTC

[jira] [Resolved] (KAFKA-5522) ListOffset should take LSO into account when searching by timestamp

     [ https://issues.apache.org/jira/browse/KAFKA-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-5522.
------------------------------------
    Resolution: Fixed

Issue resolved by pull request 3456
[https://github.com/apache/kafka/pull/3456]

> ListOffset should take LSO into account when searching by timestamp
> -------------------------------------------------------------------
>
>                 Key: KAFKA-5522
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5522
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>    Affects Versions: 0.11.0.0
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 0.11.0.1
>
>
> For a normal read_uncommitted consumer, we bound the offset returned from ListOffsets by the high watermark. For read_committed consumers, we should similarly bound offsets by the LSO. Currently we only handle the case of fetching the end offset.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)