When you set up a trigger at the beginning of the pipeline, all the later GroupByKey/Combine operations should automatically get a trigger that mostly "let's the data flow". If you can share more about your pipeline - especially code - then we could probably help more.
Kenn On Wed, May 26, 2021 at 9:11 AM Sozonoff Serge <se...@sozonoff.com> wrote: > Hi, > > Well not exactly but maybe I can do something with that. > > Is there no way to simply assign some sort of Global trigger to the entire > pipeline so do not have to define it for each Collection in question ? > > Thanks, > Serge > > > > > On 26 May 2021 at 18:01:14, Kenneth Knowles (k...@apache.org) wrote: > > You can use Window.configure() to only set the values you want to change. > Is that what you mean? > > Kenn > > On Wed, May 26, 2021 at 8:42 AM Sozonoff Serge <se...@sozonoff.com> wrote: > >> Hi All, >> >> I find myself having to pepper Window transforms all over my pipeline, I >> count about 9 in order to get my pipeline to run. Aside from the class type >> they window, all the statements are identical. >> >> A window into new GlobalWindows() using an identical trigger. >> >> Is there a way to change the trigger on the global window so I could >> avoid this extra code all over the place ? >> >> I really dont care about the windowing but its imposed since the pipeline >> is unbound and there are operations which require the window. >> >> Thanks, >> Serge >> >> >>
