alexeyinkin opened a new issue, #24991:
URL: https://github.com/apache/beam/issues/24991

   ### What needs to happen?
   
   In the Playground database we need to have examples that integration tests 
can load. To be reliable, these examples should not be changed or deletable by 
Apache Beam editors.
   
   Examples should be on both staged/deployed backend and local backend that is 
started with
   `./gradlew :playground:dockerComposeLocalUp`
   
   The source code of these examples should be structured in the directory tree 
so that new examples can be easily added in the same or other SDKs. Adding 
examples may require changes in the CI/CD code, but changing an example's 
should not require changing CI/CD code.
   
   Each of such example's output should be `<example_name> output`.
   Each of such example's logs should be `<example_name> log`.
   
   So far we need only one such example in Go. Its code is here: 
https://github.com/akvelon/beam/blob/issue24959_test-loading-url/playground/frontend/playground_components_dev/lib/src/examples/content/example.go
   It can be placed and/or renamed as is convenient.
   
   Suggested path to fetch it:
   `SDK_GO/INTEGRATION_TEST/Example`
   
   ### Issue Priority
   
   Priority: 3 (nice-to-have improvement)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam examples
   - [X] 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]

Reply via email to