robertwb opened a new issue, #28933: URL: https://github.com/apache/beam/issues/28933
### What needs to happen? We should make it easy to write integration tests for YAML features (beyond what is provided in the tested documentation and unit tests). As a large part of the surface area is IOs, it may be useful to allow sequences of pipelines (such that a write can be followed by a read). This could even be expressed as a yaml file. We may need some templating (and a specification of requirements) to make this work well (e.g. creation of temporary directories, or other stores like bigquery, pubsub, jdbc databases, etc.) To make thinks self-contained, we may want to add an AssertContains or similar transform that is a checking "inverse" of Create. To better test the cross-language bits, we should add a gradle target that ensures the right jars are built and accessible. When transforms are available from multiple providers, we should run the same test with different providers (and possibly combinations thereof) to ensure compatibility. Sub-tasks should possibly be filed for each of these. ### Issue Priority Priority: 2 (default / most normal work should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [X] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
