1u0 opened a new pull request #8495: [FLINK-12556][e2e] Extend some end-to-end tests to run with custom (input) File System implementation URL: https://github.com/apache/flink/pull/8495 ## What is the purpose of the change This pull request extends some end-to-end tests to be independent of origin of input source (be it a local file, s3 or an artificial file system plugin), provided that they all serve the same test data content. In particular, a new (dummy) file system plugin is introduced to check that different Flink cluster setups are working with additional (external) plugin in `lib` folder. Later, those tests can be modified to check that new plugin system also works in different cluster setups ([FLINK-11952](https://issues.apache.org/jira/browse/FLINK-11952)) ## Brief change log *(for example:)* - Yarn kerberos docker test is simplified (some code reuse) without changing behavior; - batch wordcount test is generalized and now hosts (deleted) shaded hadoop and shaded presto tests; - introduced a dummy FS plugin that serves hardcoded read-only contents from memory; - add some test runs that use dummy FS plugin as input source. ## Verifying this change This change added tests and can be verified as follows: - The modified end-to-end tests should pass ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / **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
