[
https://issues.apache.org/jira/browse/FLINK-18996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703640#comment-17703640
]
lincoln lee commented on FLINK-18996:
-------------------------------------
+1 to set the `minCleanUpInterval` to 0 by default.
Correctness is more important than runtime cleanup efficiency (and from
[~zicat]'s feedback, there may also be positive gains from lowering the value),
and it is recommended to provide a new option for users to meet the potential
cleanup bottleneck that may be encountered in scenarios without a subsequent
window operation, [~libenchao] [~zicat][~charles-tan] WDYT?
> Avoid disorder for time interval join
> -------------------------------------
>
> Key: FLINK-18996
> URL: https://issues.apache.org/jira/browse/FLINK-18996
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Runtime
> Reporter: Benchao Li
> Priority: Major
> Labels: auto-deprioritized-critical, auto-deprioritized-major
> Fix For: 1.17.0
>
>
> Currently, the time interval join will produce data with rowtime later than
> watermark. If we use the rowtime again in downstream, e.t. window
> aggregation, we'll lose some data.
>
> reported from user-zh:
> [http://apache-flink.147419.n8.nabble.com/Re-flink-interval-join-tc4458.html#none]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
