simsicon commented on issue #5752: URL: https://github.com/apache/dolphinscheduler/issues/5752#issuecomment-875219470
On the disadvantages mentioned about the current task node: > DS has two type of nodes. The one will sent to woker to execute, like SQL, Shell, MR etc. Another will control the workflow, like sub_process, condition etc. If I make all kinds of nodes supporting blocking, the nodes which will be sent to worker have the right to control workflow in a way. From this perspective, coupling appeared. I think the blocking is not a fully workflow controlling as it can only pause and continue the flow, not branching the flow, and the node itself should has rights and domain knowledges to determine if everything as expected. > In DAG, it is hard to recognize which node marked to be blocking node without double click to see the node detail information. Maybe just a different icon marking will do that? Sounds it should be just a UI issue. -- 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]
