[
https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656570#comment-15656570
]
Fabian Hueske commented on FLINK-4565:
--------------------------------------
It is true, the "few literals" case of {{IN}} and {{NOT IN}} can (and should)
be handled together.
Regarding the cross join issue: I think we do not need a cross join for {{IN}}
with uncorrelated subqueries. AFAIK, these can be implemented as equi-joins
(inner and outer). Also, I sent a another mail to the {{NOT IN}} thread on the
mailing list and added that we can support cross joins where one input is the
result of a global aggregation, i.e., exactly one record. The cross join
generated by Calcite for a {{NOT IN}} is exactly such a case and used to join a
single row to all rows of the other relation.
> Support for SQL IN operator
> ---------------------------
>
> Key: FLINK-4565
> URL: https://issues.apache.org/jira/browse/FLINK-4565
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Nikolay Vasilishin
>
> It seems that Flink SQL supports the uncorrelated sub-query IN operator. But
> it should also be available in the Table API and tested.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
