[
https://issues.apache.org/jira/browse/FLINK-18996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703987#comment-17703987
]
lincoln lee commented on FLINK-18996:
-------------------------------------
[~zicat] Of course, welcome for contributing this! For the option name, it is
recommended to consider a shorter name, such as
'table.exec.interval-join.min-cleanup-interval' (uses the duration type).
Also, given that this will change the default behavior of the interval-join
operator, we need to highlight this change in the release note, since 1.18 is
not yet kickoff, we can update the 'Release Note' content of this jira first.
> 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.18.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)
