GitHub user Xpray opened a pull request:

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

    [FLINK-9344] [TableAPI & SQL] Support INTERSECT and INTERSECT ALL for 
streaming

    [FLINK-9344] [TableAPI & SQL] Support INTERSECT and INTERSECT ALL for 
streaming
    
    ## What is the purpose of the change
    Support Intersect and Intersect All for Streaming SQL and TableAPI
    
    
    ## Brief change log
    * implemented StreamIntersectCoProcessFunction
    
    
    ## Verifying this change
    
    This change added tests and can be verified as follows:
    cases of intersect operations in both 
```org.apache.flink.table.runtime.stream.sql.SetOperatorsITCase```  and
    ```org.apache.flink.table.runtime.stream.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
      - The S3 file system connector:  no
    
    ## Documentation
    
      - Does this pull request introduce a new feature? yes
      - If yes, how is the feature documented?  not yet, but will be documented 
in next issue


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

    $ git pull https://github.com/Xpray/flink FLINK-9344

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

    https://github.com/apache/flink/pull/5998.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 #5998
    
----
commit 505875c9e05d0613ddc3ae304293d46780411595
Author: Xpray <leonxpray@...>
Date:   2018-05-12T15:15:09Z

    [FLINK-9344][TableAPI & SQL] Support INTERSECT and INTERSECT ALL for 
streaming

----


---

Reply via email to