[
https://issues.apache.org/jira/browse/FLINK-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323207#comment-17323207
]
Flink Jira Bot commented on FLINK-13648:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Jing Zhang
> Priority: Major
> Labels: stale-assigned
>
> 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)
