Github user twalthr commented on a diff in the pull request:
https://github.com/apache/flink/pull/2870#discussion_r104375934
--- 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 --
You are right, working with POJOs and Case classes does not always give you
best performance but limiting the number of supported types results in bad user
experience. Types that are supported in general, should also be supported by
features. Why can't we use POJOs in SQL? Is `f4 IN (f3, f2, f0)` not possible?
---
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.
---
