damondouglas opened a new issue, #30250: URL: https://github.com/apache/beam/issues/30250
### What needs to happen? Under #29669 The following uses an example driven approach via [gherkin syntax](https://cucumber.io/docs/gherkin/reference/) to describe drain behavior. ## Scenario: pipeline reads from Pub/Sub ```gherkin Given pipeline reads from Pub/Sub subscription And more messages remain in the subscription When I trigger a drain Then no more mesages are read from the Pub/Sub subscription And the pipeline processes remaining messages read before the drain was triggered ``` ## Scenario: pipeline reads from file system ```gherkin Given pipeline reads from a filesystem And more files are yet to be read by the pipeline When I trigger a drain Then the remaining files are read by the pipeline ``` ## Scenario: pipeline reads from Pub/Sub and reads from file system into a side input ```gherkin Given pipeline reads from Pub/Sub subscription And more messages remain in the subscription When I trigger a drain Then no more mesages are read from the Pub/Sub subscription And the remaining files are read by the pipeline into the side input And the pipeline processes remaining messages read before the drain was triggered ``` ## Scenario: pipeline writes to Pub/Sub topic ```gherkin Given pipeline writes to Pub/Sub topic When I trigger a drain Then the pipeline stops writing to the topic ``` ### 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 - [ ] 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]
