[
https://issues.apache.org/jira/browse/KAFKA-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300643#comment-15300643
]
Vahid Hashemian commented on KAFKA-3370:
----------------------------------------
Thanks [~gwenshap].
And it seems from the description of this JIRA that another use case is when we
don't want an auto-reset when fetching an offset that is out of range. Instead,
we would want to be notified that the requested offset does not exist. In this
case, I see a total of 4 new policies:
1,2. earliest-on-start and latest-on-start as suggested in the description with
the above semantics for out-of-range offsets
earliest-on-start: move to earliest during initialization, error for other
out-of-range offset fetches
latest-on-start: move to latest during initialization, error for other
out-of-range offset fetches
3,4. earliest-auto-correct and latest-auto-correct as you suggested earlier
earliest-auto-correct: move to earliest during initialization, otherwise: move
to earliest if offset too low for range, or to latest if offset too high for
range
latest-auto-correct: move to latest during initialization, otherwise: move to
earliest if offset too low for range, or to latest if offset too high for range
Thoughts?
> 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
> 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)
