You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/26 17:27:00 UTC

[jira] [Commented] (FLINK-4565) Support for SQL IN operator

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

ASF GitHub Bot commented on FLINK-4565:
---------------------------------------

GitHub user twalthr opened a pull request:

    https://github.com/apache/flink/pull/4404

    [FLINK-4565] [table] Support for SQL IN operator

    ## What is the purpose of the change
    
    *This PR adds support for the IN operator in both SQL and Table API. Both for testing in a set of elements `f0.in(1, 2, 3)` as well as in sub-query `f0.in(table)`*
    
    
    ## Brief change log
    
    *Various changes in plan translation, code generation, and API.*
    
    
    ## Verifying this change
    
    This change added tests and can be verified as follows:
    
      - *Unit tests: org.apache.flink.table.expressions.ScalarOperatorsTest*
      - *Unit tests: org.apache.flink.table.expressions.validation.ScalarOperatorsValidationTest*
      - *Integration tests: org.apache.flink.table.runtime.batch.sql.SetOperatorsITCase*
      - *Integration tests: org.apache.flink.table.runtime.batch.table.SetOperatorsITCase*
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): no
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no
      - The serializers: no
      - The runtime per-record code paths (performance sensitive): no
      - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
    
    ## Documentation
    
      - Does this pull request introduce a new feature? yes
      - If yes, how is the feature documented? not documented
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/twalthr/flink FLINK-4565

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4404
    
----
commit c0e7f58973cd4237382811b7ae1ee4fb4cdcaebf
Author: DmytroShkvyra <ds...@gmail.com>
Date:   2017-03-09T19:37:46Z

    [FLINK-4565] [table] Support for SQL IN operator

commit 14ff3c23e04c03c018118cc8ab33ea7255277ef9
Author: twalthr <tw...@apache.org>
Date:   2017-07-26T16:11:38Z

    [FLINK-4565] [table] Full IN operator support for literals and sub-queries

----


> 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: Timo Walther
>
> 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.4.14#64029)