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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
