[jira] [Commented] (KAFKA-3370) Add options to auto.offset.reset to reset offsets upon initialization only

["Vahid Hashemian (JIRA)" <ji...@apache.org>]

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

Vahid Hashemian commented on KAFKA-3370:
----------------------------------------

[~guozhang] Is this https://github.com/apache/kafka/compare/trunk...vahidhashemian:KAFKA-3370?expand=1 close to what you had in mind for this JIRA? Thanks.

> 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
>             Fix For: 0.10.1.0
>
>
> 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
(v6.3.4#6332)