Hi Marek,
that is because you set the timer to be relative. The baseline time will
then be set to current watermark, which is without being initialized
equal to BoundedWindow.TIMESTAMP_MIN_VALUE, which is -9223372036854775
(in millis). Adding 10000 (10 seconds) to this yields the result you
observe.
Jan
On 12/10/19 5:42 PM, marek-simu...@seznam.cz wrote:
Hi,
PROCESSING_TIME or EVENT_TIME timer reports in first trigger of
timer function in :
OnTimerContext context.timestamp()=-290308-12-21T19:59:05.225Z
PROCESSING_TIME has known unresolved issue [1], but I didn’t expect
that EVENT_TIME would report in @onTimer function weird timestamp in
first trigger
Failing example test [2].
It also happened to me with KafkaIO and FIleIO on FlinkRunner. I
noticed that in tests there is set
.advanceWatermarkTo(Instant.EPOCH) before you add elements why is that?
I am not sure what is the correct behavior and what I am doing wrong.
Thanks for advice
[1]
https://lists.apache.org/thread.html/46fbe4812624e6fec720e776bfe341b400982472a8b7b3142d846704%40%3Cdev.beam.apache.org%3E
[2]
https://github.com/seznam/beam/commit/f2175dda43e69d189651b3d519ee5327144bcdd3
