flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From twalthr <...@git.apache.org>
Subject [GitHub] flink pull request #2870: [FLINK-4565] Support for SQL IN operator
Date Mon, 06 Mar 2017 09:47:13 GMT
Github user twalthr commented on a diff in the pull request:

    --- Diff: flink-libraries/flink-table/src/test/scala/org/apache/flink/api/table/expressions/ScalarFunctionsTest.scala
    @@ -1101,6 +1101,45 @@ class ScalarFunctionsTest extends ExpressionTestBase {
    +  @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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message