Hi Maciej,
The pr is related to FLINK-21301
<https://issues.apache.org/jira/browse/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, else use
'minIdleStateRetentionTime' in table config." +
"< 0 is illegal configuration. " +
"0 means disable allow lateness. " +
"> 0 means allow-lateness.
First of all, the pr is merged to 1.14 which is not released yet.
Secondly, `table.exec.emit.allow-lateness` is experimental
<https://github.com/experimental> configuration which only works for Group
window aggregation [2], it would not effect the Window TVF aggregation.
Thirdly, `table.exec.emit.allow-lateness` configuration is back forward
compatible, it specifies allow-lateness for Group window aggregation and
state ttl can still take effect when the new config is not set `
table.exec.emit.allow-lateness`
[1] https://issues.apache.org/jira/browse/FLINK-21301
[2]
https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/table/sql/queries/window-agg/#group-window-aggregation
Maciej Bryński <mac...@brynski.pl> 于2021年8月10日周二 下午9:21写道：
> 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
>
