I am guessing you will be affected by the fact that windows processed independently for each key. Is that what you are referring to when you mention multiple isLast() windows?
Kenn On Fri, May 1, 2020 at 3:36 AM Truebody, Kyle <truebo...@dnb.com> wrote: > Hi all, > > > > We are working on a streaming pipeline that we need to compatible with out > legacy platform while we make the move over to Beam Streaming. > > Our legacy platform uses a co-ordination framework (oozie). Each step is > in the coordination pipeline is active by the creation of a trigger file. > > > > I am looking for a beam construct or flag that will notify the Context/ > driver of the closure of a Time window. We need to enable to create a > trigger flag only when all the files have been emitted > > from set window period. > > > > We have tried creating the trigger flag using the PaneInfo.isLast() > through a custom WindowFileNamePolicy. Noticed that a window has multiple > Panes that will have isLast() as true. > > > > Thanks, > > Kyle >
