Re: Allowed lateness in Flink SQL

Thanks Ingo. I will look into CURRENT_WATERMARK. About allow-lateness. I can imagine the following situation. Let's have a left interval join between two streams. I want to wait 15 minutes for events from the right stream to arrive (this can be done by setting a watermark on the right stream). Als

Re: Allowed lateness in Flink SQL

Hi Maciej, The pr is related to FLINK-21301 [1]. Sets the time by which elements are allowed to be late. Elements that arrive behind the watermark by more than the specified time " + "will be dropped. " + "Note: use the value if it is set

Re: Allowed lateness in Flink SQL

Hi Maciej, there is no documentation for it (besides in the code itself) because it's an experimental flag. What would you expect allow-lateness to do outside the context of a window? Maybe you'd also be interested in CURRENT_WATERMARK()[1][2] which will be released with 1.14 and allows some level

Allowed lateness in Flink SQL

Hi Guys, I was checking if anything changed recently with allowed lateness support in Flink SQL and I found this PR: https://github.com/apache/flink/pull/16022 Is there any documentation for table.exec.emit.allow-lateness ? Is this option working only in window agregation? Regards, -- Maciek Bry