[ 
https://issues.apache.org/jira/browse/KAFKA-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708109#comment-14708109
 ] 

Neha Narkhede commented on KAFKA-2390:
--------------------------------------

seek() is meant to update internal fetch position that the consumer uses on the 
next poll(). It updates an in-memory offest value on the consumer and does not 
involve a roundtrip to the server. So a callback here doesn't make much sense. 
[~lindong] [~becket_qin] Can you guys explain the purpose of these API changes?
cc [~hachikuji]

> Seek() should take a callback.
> ------------------------------
>
>                 Key: KAFKA-2390
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2390
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jiangjie Qin
>            Assignee: Dong Lin
>
> Currently seek is an async call. To have the same interface as other calls 
> like commit(), seek() should take a callback. This callback will be invoked 
> if the position to seek triggers OFFSET_OUT_OF_RANGE exception from broker.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to