[
https://issues.apache.org/jira/browse/KAFKA-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709854#comment-14709854
]
Jiangjie Qin commented on KAFKA-2390:
-------------------------------------
Do you mean we have something like:
{code}
class OffsetOutOfRangeException {
TopicPartition tp;
long fetchPosition;
}
{code}
I am thinking what user would do after receiving this exception? I guess most
of them would want to do some state cleanup and then either reset offset to
earliest or latest or throw out the exception. So it seems useful to provide
the log starting or ending offset in the exception as well, right?
> 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)
