Good job, Solution 1 seems like better. By the way, I'm a little confused about why success is an option. When the task runs successfully, it will continue to execute the next task. Usually we can set "Failure to continue"
Best Regards --------------- Apache DolphinScheduler PMC Chair David [email protected] Linkedin: https://www.linkedin.com/in/dailidong Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> --------------- On Tue, Jul 6, 2021 at 9:36 PM 黄智远 <[email protected]> wrote: > Sorry! The issue hyperlink may NOT appear in the mail. I add the issue > address blow, you can follow that to get more information. > https://github.com/apache/dolphinscheduler/issues/5752 > > =================== > Stay Hungry, Stay Foolish > Martin Huang > [email protected] > Sent with a Spark > =================== > 在 2021年7月5日 +0800 PM11:35，黄智远 <[email protected]>，写道： > > This is a new feature, let me make a brief introduction. > > > > Normally, we execute the whole workflow from start to the end. But > sometimes, we want to pause the workflow to check the intermediate result. > If correct, execution process continue. If not, pause the workflow and > inform someone to solve it. So, I propose blocking task. The aim of > blocking task is to pause the execution process properly based on user > settings. Now, I come up with two solutions: > > Solution I: Modify current node to support this feature. > > Solution II: Add a new type of node. > > > > I want to know which solution is more appropriate. If you interested in > this feature, you can follow this link to learn more about blocking task > and my solutions. > > > > Best Regards > > > > =================== > > Stay Hungry, Stay Foolish > > Martin Huang > > [email protected] > > Sent with a Spark > > =================== >
