ruanwenjun commented on issue #18265: URL: https://github.com/apache/dolphinscheduler/issues/18265#issuecomment-4456495630
I agree that there are issues with the current interaction logic and the parameter configurations for some tasks and workflows (many of these issues have been around for a long time; we are gradually addressing them, but progress is slow). Many of the cumbersome steps involved here have historical roots; for example, changes require offline workflow. These measures are intended to enhance security, and historically, many users have built approval workflows around them. Actually, I also believe that tasks can be treated as first-class citizens, but this would require a series of architectural changes, and I haven’t figured out how to do that yet. Most open-source projects are maintained by contributors on a volunteer basis; while some historical design choices may seem suboptimal, these efforts deserve respect. I’m going to close this issue. We’d prefer to see specific, constructive issues rather than hostile questions about why we did something that’s already been implemented. -- 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]
