[
https://issues.apache.org/jira/browse/FLINK-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu resolved FLINK-13433.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
[table-planner-blink] Do not fetch data from LookupableTableSource if the
JoinKey in left side of LookupJoin contains null value
- master: 4b48eb89283f1d61514a4a52263d8291b724da90
- 1.9: 8b2680ad182601f18d9998eb8dd38675e5c3d5c5
[table-planner-blink] Forbidden `IS NOT DISTINCT FROM `(or an expanded version)
in LookupJoin.
- master: 78d1e68ab120e2fecb931e6d9ea1ee8bef247cde
- 1.9: 7838436fc3b3aa653ecb33fc965116110b1f835e
> Do not fetch data from LookupableTableSource if the JoinKey in left side of
> LookupJoin contains null value
> ----------------------------------------------------------------------------------------------------------
>
> Key: FLINK-13433
> URL: https://issues.apache.org/jira/browse/FLINK-13433
> Project: Flink
> Issue Type: Task
> Components: Table SQL / Planner
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Jing Zhang
> Assignee: Jing Zhang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Attachments: LookupJoinITCase.scala
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> For LookupJoin, if joinKey in left side of a LeftOuterJoin/InnerJoin contains
> null values, there is no need to fetch data from `LookupableTableSource`.
> However, we don't shortcut the fetch function under the case at present, the
> correctness of results depends on the `TableFunction` implementation of each
> `LookupableTableSource`.
> I add some testcases in
> `org.apache.flink.table.planner.runtime.stream.sql.LookupJoinITCase`, the
> results are all unexpected.
> More detail cases could be find in patch.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
