You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Jing Zhang (JIRA)" <ji...@apache.org> on 2019/07/31 10:11:00 UTC
[jira] [Created] (FLINK-13509) Support `is not distinct from ` and
similar syntax in LookupJoin
Jing Zhang created FLINK-13509:
----------------------------------
Summary: Support `is not distinct from ` and similar syntax in LookupJoin
Key: FLINK-13509
URL: https://issues.apache.org/jira/browse/FLINK-13509
Project: Flink
Issue Type: Task
Components: Table SQL / Planner
Affects Versions: 1.10.0
Reporter: Jing Zhang
Fix For: 1.10.0
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 error.Because LookupJoin does not handle the case correctly.
Here is plan:
In 1.9 version, simply throw exception in compile phase for the above sql.
Support the feature in 1.10 version.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)