[
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-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> 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: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> 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)
