[
https://issues.apache.org/jira/browse/FLINK-19063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186253#comment-17186253
]
Paul Lin commented on FLINK-19063:
----------------------------------
WRT event-time temporal table join, as an initial and naive thought, I think we
can leverage the watermarks of both streams (may require some watermark
mechanism changes). We should ensure the build side watermark is greater than
the one of the probe size, if not, maybe we can keep the unjoined data of the
probe side table before the build side watermark(plus allowed lateness) in the
states.
When a new element of the build side shows up, it triggers the unjoined data in
the states to re-join, produce the join result (if any), and be removed from
the states. The process would be similar to event-time interval join.
> Support join late event from dimension table side in temporal table join
> -------------------------------------------------------------------------
>
> Key: FLINK-19063
> URL: https://issues.apache.org/jira/browse/FLINK-19063
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Leonard Xu
> Priority: Major
>
> To join late event from dimension table side in temporal table join is a
> common user case
> from user-zh mail list[1][2].
> And another similar user case is how to enable the faster stream to wait the
> slower stream in regular stream join[3].
> I think we can discuss how to support these user cases.
>
>
> [1][http://apache-flink.147419.n8.nabble.com/Flink-join-td6563.html]
> [2][http://apache-flink.147419.n8.nabble.com/flinksql-mysql-td3584.html#a3585]
> [3][http://apache-flink.147419.n8.nabble.com/Flink-sql-td4435.html#a4436]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
