Ah OK! Thanks! On Mon, Feb 6, 2017, 3:09 PM Eno Thereska <eno.there...@gmail.com> wrote:
> Oh, by "other" I meant the original one you started discussing: > COMMIT_INTERVAL_MS_CONFIG. > > Eno > > On 6 Feb 2017, at 09:28, Mahendra Kariya <mahendra.kar...@go-jek.com> > wrote: > > > > Thanks Eno! > > > > I am just wondering what is this other commit parameter? > > > > On Mon, Feb 6, 2017, 12:52 PM Eno Thereska <eno.there...@gmail.com> > wrote: > > > >> Hi Mahendra, > >> > >> That is a good question. Streams uses consumers and that config applies > to > >> consumers. However, in streams we always set enable.auto.commit to > false, > >> and manage commits using the other commit parameter. That way streams > has > >> more control on when offsets are committed. > >> > >> Eno > >>> On 6 Feb 2017, at 05:39, Mahendra Kariya <mahendra.kar...@go-jek.com> > >> wrote: > >>> > >>> I have another follow up question regarding configuration. > >>> > >>> There is a config for enable.auto.commit for consumers. Does this apply > >> to > >>> Kafka streams? If yes, how is the behavior different when the value of > >> this > >>> config is true vs false? > >>> > >>> More generally, which of the consumer configs > >>> <https://kafka.apache.org/documentation/#consumerconfigs> apply to > Kafka > >>> streams as well? > >>> > >>> > >>> > >>> > >>> On Fri, Feb 3, 2017 at 9:43 PM, Mahendra Kariya < > >> mahendra.kar...@go-jek.com> > >>> wrote: > >>> > >>>> Ah OK! Thanks a lot for this clarification. > >>>> > >>>> it will only commit the offsets if the value of > >> COMMIT_INTERVAL_MS_CONFIG > >>>>> has > >>>>> passed. > >>>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >> > >> > >
