[
https://issues.apache.org/jira/browse/KAFKA-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15531675#comment-15531675
]
Bill Bejeck commented on KAFKA-4114:
------------------------------------
No worries on the response.
Thanks for clearing things up. I knew the first case was covered by the
StreamsConfigs settings but my confusion stemmed from when I took a look at the
{{Consumer}} interface, I completely missed the {{seekToEnd()}} and
{{seekToBegining()}} methods taking a {{Collection<TopicPartition>}}
parameter, thus enabling the 'fine grained' control per topic. I think this is
precisely the approach to take vs multiple consumers.
>From now on I think I will institute a self-imposed 24 hour hold on all
>questions.
Thanks for the comments.
> 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)
