[
https://issues.apache.org/jira/browse/KAFKA-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067175#comment-16067175
]
ASF GitHub Bot commented on KAFKA-5522:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/3456
KAFKA-5522: ListOffsets should bound timestamp search by LSO in
read_committed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-5522
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3456.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3456
----
commit 99bb1b1ee84815f3a2553aad297d2019b12d1c3d
Author: Jason Gustafson <ja...@confluent.io>
Date: 2017-06-28T20:26:08Z
KAFKA-5522: ListOffsets should bound timestamp search by LSO in
read_committed
----
> 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)
