Re: Beam/Samza Ensuring At Least Once semantics

2019-07-12 Thread Lukasz Cwik
"Audo, > Nicholas" , "Cesar, Scott" < > scott_ce...@intuit.com>, "Ho, Tom" , " > d...@samza.apache.org" > *Subject: *Re: Beam/Samza Ensuring At Least Once semantics > > > > This email is from an external sender. > > > >

Re: Beam/Samza Ensuring At Least Once semantics

2019-07-10 Thread Lukasz Cwik
g’, ‘h’, ‘I’, ‘j’ from input topic and process > these records. > > > > Results > > After I restarted app, it does NOT re-process ‘g’, ‘h’, ‘I’, ‘j’ values. > If I add new value ‘k’ into input topic, I see “read from topic=XXX, > part=0, offset=106, val: k”, and after some t

Re: Beam/Samza Ensuring At Least Once semantics

2019-07-09 Thread Benenson, Mikhail
with values ‘g’, ‘h’, ‘I’, ‘j’ are NOT processed. Based on these results I’m incline to conclude that Beam with Samza runner does NOT provides 'at least once' guarantee for processing. If I missed something? -- Michael Benenson From: "LeVeck, Matt" Dat