[
https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897015#comment-15897015
]
ASF GitHub Bot commented on FLINK-4565:
---------------------------------------
Github user DmytroShkvyra commented on a diff in the pull request:
https://github.com/apache/flink/pull/2870#discussion_r104379120
--- Diff:
flink-libraries/flink-table/src/test/scala/org/apache/flink/api/table/expressions/ScalarFunctionsTest.scala
---
@@ -1101,6 +1101,45 @@ class ScalarFunctionsTest extends ExpressionTestBase
{
"true")
}
+ @Test
+ def testInExpressions(): Unit = {
+ testTableApi(
--- End diff --
@twalthr It's a big problem. Even two problems:
1. We mention that that all types (right) in IN operator have the same type
because we use Set as collection. And we check if right operand has only one
`TypeInfo`. Otherwise we should check each item one by one or use something
like bloom filter
2. Problem with compilation of expression - each field is compiling to more
simple type (the most big problem)
> 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: Dmytro Shkvyra
>
> 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.15#6346)
