[
https://issues.apache.org/jira/browse/KAFKA-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531570#comment-15531570
]
Matthias J. Sax commented on KAFKA-4114:
----------------------------------------
Sorry for the late reply. Case #1 is already supported right now. Because there
is a single Consumer, it's reset policy is configured via eg
{{StreamConfig#put(ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "latest");}} which
applies for all stream/table that are consumed. This JIRA should enable case
#2. However, I think we do not need multiple consumers. I would rather set
default value for this consumer config as {{"none"}} and use
{{seekToBeginning()}} and {{seekToEnd()}} according to the provided reset
strategy per stream/table to the manually reset the offset instead of relying
on consumer's internal reset. WDYT? Maybe [~guozhang] also want to comment?
> Allow for different "auto.offset.reset" strategies for different input streams
> ------------------------------------------------------------------------------
>
> Key: KAFKA-4114
> URL: https://issues.apache.org/jira/browse/KAFKA-4114
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Bill Bejeck
>
> Today we only have one consumer config "offset.auto.reset" to control that
> behavior, which means all streams are read either from "earliest" or "latest".
> However, it would be useful to improve this settings to allow users have
> finer control over different input stream. For example, with two input
> streams, one of them always reading from offset 0 upon (re)-starting, and the
> other reading for log end offset.
> This JIRA requires to extend {{KStreamBuilder}} API for methods
> {{.stream(...)}} and {{.table(...)}} to add a new parameter that indicate the
> initial offset to be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
