GitHub user NicoK opened a pull request:

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

    [FLINK-9839][e2e] add a streaming allround test with SSL enabled

    ## What is the purpose of the change
    
    Currently, there's no simple streaming job test like the 
`test_batch_allround.sh` and none of the other streaming tests uses SSL.
    
    ## Brief change log
    
    - add tools to enable SSL in the config (including key generation)
    - create `test_streaming_allround.sh` (with SSL enabled) verifying that 
this job runs
    - add `test_streaming_allround.sh` to `run-pre-commit-tests.sh`
    
    ## Verifying this change
    
    This change is a test but currently does not work because of 
https://issues.apache.org/jira/browse/FLINK-9842
    
    ## 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/NicoK/flink flink-9839

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

    https://github.com/apache/flink/pull/6327.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 #6327
    
----
commit 05b88d9afcda6d0a4385dccf77b50dd023c1ef54
Author: Nico Kruber <nico@...>
Date:   2018-07-13T08:39:55Z

    [FLINK-9839][e2e] add a streaming allround test with SSL enabled

----


---

Reply via email to