>This is very surprising behavior to me and I don't see a good reason for this >being the case. Why is this the case in the Java SDK?
If you look at `GlobalWindow`, it explains that triggers use `maxTimestamp()` to set the timer. A trigger is triggered when the Watermark passes the trigger time. So this was initially introduced to be able to trigger global windows, which used MAX_TIMESTAMP previously. > Shouldn't we make the formal spec do the more obvious thing rather than carry > over what seems like a longstanding hack from one SDK to the formal spec? Would be desirable to fix this, e.g. have a special rule for triggers to always fire at MAX_TIMESTAMP. [ Full content available at: https://github.com/apache/beam/pull/6315 ] This message was relayed via gitbox.apache.org for [email protected]
