Add ValidatesRunner test for non-blocking job submission
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
At the very least the Flink Runner does not support non-blocking job submission and `PipelineResult.cancel()`/`.waitUntilFinish()`. (BEAM-593)
The PR for BEAM-593 contains a test for this that is specific to the Flink Runner. This can easily be implemented as a `ValidatesRunner` test.
Imported from Jira [BEAM-2315](https://issues.apache.org/jira/browse/BEAM-2315). Original Jira may contain additional context.
Reported by: aljoscha.
Contributor guide
Research direction
Start by locating the Flink Runner-specific test from the BEAM-593 pull request and the existing ValidatesRunner tests. Adapt the non-blocking job submission coverage to the shared ValidatesRunner suite, including PipelineResult.cancel() and waitUntilFinish(), and confirm the test exposes the unsupported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100