> Regarding the event-time processing and watermarking, I have got that if
> an event will be received late, after the allowed lateness time, it will be
> dropped even though I think it is an antithesis of exactly-once semantic.
>
> Yes, allowed lateness is a compromise between exactly-once semanti
Hi Mohammad
I expected to find a description of a mechanism for detecting and ignoring
duplicate events in the documentation, although I got the two-phase commit
protocol issuing something utterly different.
Flink would not detect and ignore duplicate events when processing them but
ensure chec
