Re: How to fire the global window when using GroupAlsoByWindowViaWindowSetDoFn?

[Kenneth Knowles]

Hi Shen,

Your runner should advance the watermark for the PCollection coming out of
the BoundedSource to BoundedWindow.MAX_TIMESTAMP, which is "positive
infinity" and indicates that even the global window has fired/expired (for
the global window these are the same instant).

Kenn

On Tue, Jan 31, 2017 at 8:32 PM, Shen Li  wrote:

> Hi,
>
> My runner is translating GroupByKey using
> GroupAlsoByWindowViaWindowSetDoFn. Say I have a BoundedSource with five
> tuples all placed into a global window. When the source is depleted, how
> should the runner notify the downstream
> GroupByKey(GroupAlsoByWindowViaWindowSetDoFn) that it should fire the
> global window?
>
> Thanks,
>
> Shen
>

How to fire the global window when using GroupAlsoByWindowViaWindowSetDoFn?

[Shen Li]

Hi,

My runner is translating GroupByKey using
GroupAlsoByWindowViaWindowSetDoFn. Say I have a BoundedSource with five
tuples all placed into a global window. When the source is depleted, how
should the runner notify the downstream
GroupByKey(GroupAlsoByWindowViaWindowSetDoFn) that it should fire the
global window?

Thanks,

Shen