[
https://issues.apache.org/jira/browse/FLINK-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13648:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Support "IS NOT DISTINCT FROM" operator in lookup join
> ------------------------------------------------------
>
> Key: FLINK-13648
> URL: https://issues.apache.org/jira/browse/FLINK-13648
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
> Reporter: Jark Wu
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> Example1:
> {code:java}
> `SELECT T.id, T.len, T.content, D.name FROM T JOIN userTable for system_time
> as of T.proctime AS D ON T.id = D.id OR (T.id is null and D.id is null)`
> {code}
> Example2:
> {code:java}
> "SELECT T.id, T.len, T.content, D.name FROM T JOIN userTable for system_time
> as of T.proctime AS D ON T.id IS NOT DISTINCT FROM D.id"
> {code}
> Now run the above sql in Blink planner, the results are not expected.Because
> LookupJoin does not handle the case correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
