Thanks! On Thu, Feb 23, 2017 at 10:49 AM, Guozhang Wang <wangg...@gmail.com> wrote:
> Mahendra, > > That is right, what I meant is that at the end of each loop in the thread, > it will check against the commit internal and see if it should do so. That > means, commit will only happen after any records have been completely > processed in the topology, and that also means that the actual commit > internal may be a bit longer than the configured value in practice. > > > Guozhang > > > > On Wed, Feb 22, 2017 at 8:15 PM, Mahendra Kariya < > mahendra.kar...@go-jek.com > > wrote: > > > Hi Guozhang, > > > > On Thu, Feb 23, 2017 at 2:48 AM, Guozhang Wang <wangg...@gmail.com> > wrote: > > > > > With that even if you do > > > not have any data processed the commit operation will be triggered > after > > > that configured period of time. > > > > > > > The above statement is confusing. As per this thread < > http://goo.gl/yczQpy > > >, > > offsets are only committed once they have been fully processed by the > > topology and not when the timeout expires! > > > > > > -- > -- Guozhang >
