I meant issues with windows firing before their time (i.e. before the watermark passes the end of the window).
On Thu, Feb 6, 2020 at 8:42 PM Kenneth Knowles <[email protected]> wrote: > > What is an out of order window? > > On Thu, Feb 6, 2020 at 3:09 PM Sam Rohde <[email protected]> wrote: >> >> Gotcha, I was just surprised by the precision loss. Thanks! >> >> On Thu, Feb 6, 2020 at 1:50 PM Robert Bradshaw <[email protected]> wrote: >>> >>> Yes, the inconsistency of timestamp granularity is something that >>> hasn't yet been resolved (see previous messages on this list). As long >>> as we round consistently, it won't result in out-of-order windows, but >>> it may result in timestamp truncation and (for sub-millisecond small >>> windows) even window identifiaction. >>> >>> On Thu, Feb 6, 2020 at 1:42 PM Sam Rohde <[email protected]> wrote: >>> > >>> > Hi All, >>> > >>> > I saw that in the Python SDK we encode WindowedValues and Timestamps as >>> > millis, whereas the TIME_GRANULARITY is defined as 1us. Why do we do >>> > this? Won't this cause problems using the FnApiRunner as windows might >>> > fire out of order or something else? >>> > >>> > Thanks, >>> > Sam
