[
https://issues.apache.org/jira/browse/FLINK-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949995#comment-15949995
]
Fabian Hueske commented on FLINK-5725:
--------------------------------------
Hi [~Yuhong_kyo], sorry for the late feedback on your design document.
I think your approach is good. I would also prefer the ProcessFunction.
I think it makes sense to break this issue up into multiple sub-issues.
- I would (initially) not support non-equi or cross joins
- As a first approach, I would go for inner joins
- Outer joins will be more tricky, because you need to defer the emission of
the null-join result until it is guaranteed that no other matching row will
arrive.
- the state management and clean up strategies depend on the predicate type.
There could also be {{o.proctime BETWEEN s.proctime - INTERVAL '1' HOUR AND
s.proctime}} or {{o.proctime BETWEEN s.proctime - INTERVAL '1' HOUR AND
s.proctime + INTERVAL '1' HOUR}}. I think these cases should also be covered by
an initial implementation.
What do you think?
> Support JOIN between two streams in the SQL API
> -----------------------------------------------
>
> Key: FLINK-5725
> URL: https://issues.apache.org/jira/browse/FLINK-5725
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Haohui Mai
> Assignee: hongyuhong
>
> As described in the title.
> This jira proposes to support joining two streaming tables in the SQL API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
