mgsky1 opened a new pull request #6272: URL: https://github.com/apache/dolphinscheduler/pull/6272
This PR is reference to issue[#5752](https://github.com/apache/dolphinscheduler/issues/5752) ## Brief changelog This PR contains two parts: - Blocking task java code - Blocking task UT These changes are based on ds 2.0 architecture. ## Brief Introduction > Note: The screen shoots come from my [add-blocking-task-dev](https://github.com/mgsky1/dolphinscheduler/tree/add-blocking-task-dev) which based on ds 1.x architecture. In this part, serval pictures with simple introduction will let you know what blocking task looks like. Now, suppose we have a work flow: <img width="648" alt="demo-01" src="https://user-images.githubusercontent.com/23556693/132489372-b7ab2bc4-1afe-4c4a-89b0-412de3b2aa87.png"> The node with dolphin icon is a blocking node. It will check weather the execution process meet our requirement. The blocking node settings UI is shown below <img width="710" alt="demo-02" src="https://user-images.githubusercontent.com/23556693/132489456-e4952c13-b8ef-420a-848f-b7f0b0521fef.png"> We can choose blocking condition, alert option and edit blocking logic in custom parameters. Now, I will show you THREE scenarios: None-Blocking, Blocking-with-No-Alert, Blocking-with-Alert None Blocking: <img width="737" alt="demo-03" src="https://user-images.githubusercontent.com/23556693/132489553-1b657e31-7dab-4ccc-83f9-793261785714.png"> Blocking-with-No-Alert The process will be paused and the tasks after blocking node will not be submitted. <img width="1215" alt="demo-04" src="https://user-images.githubusercontent.com/23556693/132489621-e481ee13-97b8-4c6c-be26-52a6bdec3e36.png"> <img width="1208" alt="demo-05" src="https://user-images.githubusercontent.com/23556693/132489652-8fa59017-905d-40d7-9d89-e7cf0ebfa0c2.png"> Blocking-with-Alert After the process blocked, an email will be sent to you <img width="915" alt="demo-06" src="https://user-images.githubusercontent.com/23556693/132489705-fecb9403-93e9-44c1-a6eb-a28c7816d85f.png"> -- 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]
