GitHub user deepaks4077 opened a pull request:

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

    [FLINK-9563]: Using a custom sink function for tests in CEPITCase instead 
of writing to disk

    ## What is the purpose of the change
    
    This change modifies the CEPITCase integration test to use a custom sink 
function to collect and compare test results, instead of writing them to a 
file. It does not add/remove any constituent tests.
    
    ## Brief change log
    
    - Removed Before and After junit annotations
    - Added a custom sink function with a static arraylist to collect and 
compare test results
    
    ## Verifying this change
    
    This change is already covered by existing tests, such as CEPITCase, which 
is the end to end test of the CEP API.
    
    ## 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? no
      - If yes, how is the feature documented? not applicable


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

    $ git pull https://github.com/deepaks4077/flink FLINK-9563

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

    https://github.com/apache/flink/pull/6170.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 #6170
    
----
commit 8fc629a557af4a56ab7638cc5eb519e163267cdc
Author: Deepak Sharnma <deepaks4077@...>
Date:   2018-06-13T02:41:27Z

    [FLINK-9563]: Using a custom sink function for tests in CEPITCase

----


---

Reply via email to