[
https://issues.apache.org/jira/browse/FLINK-23305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23305:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Support semi/anti interval joins
> --------------------------------
>
> Key: FLINK-23305
> URL: https://issues.apache.org/jira/browse/FLINK-23305
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
> Reporter: Timo Walther
> Assignee: Yang Xu
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> I don't see a reason why we shouldn't support interval joins also for
> semi/anti joins like:
> {code}
> SELECT *
> FROM OT
> WHERE EXISTS (
> SELECT *
> FROM TT
> WHERE TT.tx = OT.tx AND
> TT.isEnd = TRUE AND
> TT.rowtime BETWEEN OT.rowtime AND OT.rowtime + INTERVAL '1' HOUR)
> {code}
> The resulting plan contains a join operation anyway but without detecting the
> interval.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
