ZwxwZ opened a new issue, #37136: URL: https://github.com/apache/beam/issues/37136
### What happened? When using Apache Beam tests based on the documentation (https://beam.apache.org/documentation/sdks/yaml-testing/), I encountered an issue where my externally defined provider could not be recognized or used. This means I was only able to use the built-in providers provided by Apache Beam. I believe this contradicts the statement in the documentation: "Though the various built-in (and externally provided) transform in a Beam YAML pipeline can be expected to be well ### Issue Priority Priority: 2 (default / most bugs 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: Infrastructure - [ ] 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]
