openinx opened a new pull request #10106: [FLINK-11463][e2e] Design the e2e java framework so that at least the Kafka streaming tests can run on it URL: https://github.com/apache/flink/pull/10106 ## What is the purpose of the change We’ve designed a new Java e2e test framework so that we can integrate more external system , such as run test on distributed flink cluster, on distributed Kafka cluster. we accomplish the features in this Pull request: 1. Abstract the Flink resources, and provide standalone implementation .so that the test can run on different flink env. The distributed implementation have not been provided now, would better be another PR if neccesary. 2. Abstract the Kafka resources, and provide a standalone implementation. 3. Provide the annotations to separate all the e2e tests, now we provide TravisGroup1~TravisGroup6 level, each level means the nightly tests management in .travis.yaml file. 4. Provide a file cache to avoid the duplicated packages downloading ( which may timeout the test ). ## Brief change log - 2b17535918 Provide a JobSubmission class which wrap the ./bin/flink command, so that we can submit flink job by flink shell in java. - d2f308efaa Introduce the flink resource. -a486e00b20 download cache. - 4c8586d55c Introduce the Kafka resource and kafka tests. ## Verifying this change This change added tests and can be verified as follows: ```bash mvn verify -DdistDir=/Users/openinx/software/flink/build-target -Dtest=StreamingKafkaITCase -pl org.apache.flink:flink-end-to-end-tests-common ``` ## 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 documented)
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
