[
https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938708#comment-17938708
]
Akshesh Doshi commented on KAFKA-3370:
--------------------------------------
Hi
We had an issue with our Kafka consumers recently, where the
`nearest.offset.reset` feature suggested by Tayida would have been useful.
Is this something we are expecting to have soon?
> Add options to auto.offset.reset to reset offsets upon initialization only
> --------------------------------------------------------------------------
>
> Key: KAFKA-3370
> URL: https://issues.apache.org/jira/browse/KAFKA-3370
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Vahid Hashemian
> Priority: Major
> Labels: needs-kip
>
> Currently "auto.offset.reset" is applied in the following two cases:
> 1) upon starting the consumer for the first time (hence no committed offsets
> before);
> 2) upon fetching offsets out-of-range.
> For scenarios where case 2) needs to be avoid (i.e. people need to be
> notified upon offsets out-of-range rather than silently offset reset),
> "auto.offset.reset" need to be set to "none". However for case 1) setting
> "auto.offset.reset" to "none" will cause NoOffsetForPartitionException upon
> polling. And in this case, seekToBeginning/seekToEnd is mistakenly applied
> trying to set the offset at initialization, which are actually designed for
> during the life time of the consumer (in rebalance callback, for example).
> The fix proposal is to add two more options to "auto.offset.reset",
> "earliest-on-start", and "latest-on-start", whose semantics are "earliest"
> and "latest" for case 1) only, and "none" for case 2).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
