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). Also I want to update the join result if events from the right stream are more than 15 minutes late. (this can be possibly handled by allow-lateness).
Regards, Maciek wt., 10 sie 2021 o 15:38 Ingo Bürk <i...@ververica.com> napisał(a): > > 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 of late data handling. > > [1] https://issues.apache.org/jira/browse/FLINK-22737 > [2] > https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/table/functions/systemfunctions/#temporal-functions > > > Best > Ingo > > On Tue, Aug 10, 2021 at 3:21 PM Maciej Bryński <mac...@brynski.pl> wrote: >> >> 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ński -- Maciek Bryński
