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 <sro...@google.com> 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
