Triggers in beam are non-determanistic; both behaviors are acceptable (especially for batch mode). In practice, production runners evaluate triggers (e.g. in this case "do I have at least two elements") whenver a new batch of data comes in (for the Python direct runner, in batch mode, all the data comes in at once). To have more control over this you can use TestPipeline, which will attempt to fire triggers as eagerly as possible.
On Mon, Aug 17, 2020 at 1:16 PM Leiyi Zhang <[email protected]> wrote: > > for GBK wtih AfterCount(3), java sdk results in this and python sdk results > in this > > for global count with aftercount(2), java sdk results in 2 2 2 2 and python > sdk results in 8. > > On Mon, Aug 17, 2020 at 12:40 PM Robert Bradshaw <[email protected]> wrote: >> >> What results do you get in each? >> >> On Mon, Aug 17, 2020 at 11:55 AM Leiyi Zhang <[email protected]> wrote: >> > >> > Hi everyone! >> > I noticed that the behavior of AfterCount() trigger seems to be different >> > between python sdk and the java one, so I created a few tests to show the >> > difference, but in general I think the python sdk will buffer on result >> > instead of input elements. >> > >> > What do you guys think? >> > >> > and here are the tests. I ran them in batch mode. >> > >> > Sincerely, >> > Leiyi
