[
https://issues.apache.org/jira/browse/FLINK-18996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703105#comment-17703105
]
lincoln lee commented on FLINK-18996:
-------------------------------------
Besides a same issue reported in FLINK-31212, another user reported this in the
[user thread|https://lists.apache.org/thread/1t2zgf41n3q7tcb56kxo9f9qygt4g69c].
Current cleanup semantics need to be revisited since it affect the downstream
operators, e.g., an interval join followed by a window aggregate.
> 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)
