[
https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903654#comment-15903654
]
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_r105244663
--- 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 Unfortunately, add support for POJO and tuples as a standard types
of data in table API is too complicated task and out of scope this task. Adding
of new composite types to API more wide than add IN operator, it will impact
all process of validation and execution of SQL statements. It would be better
create epic for introduce new types.
I have researched it and I think I would be better commit IN operator
functionality without support tuples and POJOs. Otherwise, It would become
infinite task.
> 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)
