You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/12 04:32:16 UTC

[jira] [Commented] (KAFKA-4114) Allow for different "auto.offset.reset" strategies for different input streams

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

ASF GitHub Bot commented on KAFKA-4114:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/2007


> 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
>             Fix For: 0.10.2.0
>
>
> 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)