flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4565) Support for SQL IN operator
Date Thu, 02 Mar 2017 17:55:45 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892689#comment-15892689
] 

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_r103987812
  
    --- 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 Are you sure? That we need use IN with POJOs/Tuples/Case classes?
    First of all I will hit performance because compare of these types too complicated. it's
easier get subset of id's and use IN than compare POJOs and Case classes. More over we cant
it use in SQL string statements (we need parse POJO and case classes from string)


> 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)

Mime
View raw message