tkaymak opened a new issue, #40120: URL: https://github.com/apache/beam/issues/40120
Follow up from #40103 (review by @Abacn). `SparkStructuredStreamingPipelineResult.cancel()` requests cancellation asynchronously and sets the state to CANCELLED at once. Per the `PipelineResult` contract the state should be observed: `getState()` queries the execution, `waitUntilFinish()` blocks until the pipeline is actually cancelled on the (mini) cluster, and only then the state becomes CANCELLED. Changing this touches the shared `StructuredStreamingPipelineStateTest`, which asserts CANCELLED right after `cancel()` for the batch path today, and the legacy `SparkPipelineResult` has the same shape. Scope: `runners/spark/src/main/java/org/apache/beam/runners/spark/structuredstreaming/SparkStructuredStreamingPipelineResult.java` and that test. Part of #36841. -- 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]
