Hi,
as part of [1] a new set of validatesRunner tests has been introduced.
These tests (currently marked as category UsesStrictTimerOrdering)
verify that runners fire timers in increasing timestamp under all
circumstances. After adding these validatesRunner tests, Samza [2] and
Portable Flink [3] started to fail these tests. I have created the
tracking issues for that, because that behavior should be fixed (timers
in wrong order can cause erratic behavior and/or data loss).
I'm writing to anyone interested in solving these issues.
Cheers,
Jan
[1] https://issues.apache.org/jira/browse/BEAM-7520
[2] https://issues.apache.org/jira/browse/BEAM-8459
[3] https://issues.apache.org/jira/browse/BEAM-8460
