KarmaGYZ opened a new pull request #10538: [Flink-15135][e2e][Mesos] Adding e2e 
tests for Flink's Mesos integration
URL: https://github.com/apache/flink/pull/10538
 
 
   ## What is the purpose of the change
   
   This PR adds e2e tests for Flink's Mesos integration.
   
   ## Brief change log
   
   - 
[56588e1](https://github.com/apache/flink/commit/56588e199a463564b92039ce590821ddab1e3c9d)..[fa10c39](https://github.com/apache/flink/commit/fa10c393215803621e198ff64939c969b3108c93):
 Hotfixes, refactors and code clean-ups.
   - 
[6e4fb08](https://github.com/apache/flink/commit/6e4fb08ea363c442395053f85fd5b6a114ebcfb5):
 Adding the Dockerfile and Compose file for building docker images and 
deploying Mesos cluster using docker-compose.
   - 
[dc64604](https://github.com/apache/flink/commit/dc646045124dd6b5af2fcd3f8b11039a6265ac26):
 Facilities for maintaining Mesos cluster and running Flink on it.
   - 
[f8d11c9](https://github.com/apache/flink/commit/f8d11c92b2041f3655ec6bae42228b8ec45cd74f):
 WordCount e2e tests for Flink's Mesos integration
   - 
[41ed3d4](https://github.com/apache/flink/commit/41ed3d467603e389c84f8fd6761a4ffc3c6786e7):
 Enable the Mesos e2e test in Travis.
   
   ## Verifying this change
   
   This change is independent with Flink core code and belong to end to end 
test.
   
   ## 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
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to