[
https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655847#comment-15655847
]
Jark Wu commented on FLINK-4565:
--------------------------------
Thank you [~fhueske] for the detailed internals.
Regarding the subissue-1, could NOT IN with less than 20 literals go with this
issue together ? Because they can share many common code.
Regarding the subissue-2 and -3, I'm afraid they will involve cross join too.
As you mentioned in this [mailing
list|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/FLINK-4541-Support-for-SQL-NOT-IN-operator-td14464.html],
you would like to avoid introduce cross join. So would subissue-2 and -3 not
be supported at this point ?
> 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)
