EricGao888 opened a new issue #9249: URL: https://github.com/apache/dolphinscheduler/issues/9249
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description * Currently in dolphin scheduler, all task plugins are put under the same folder `dolphinscheduler-task-plugin`. This could lead to several potential issues when integrated with different cloud providers. ### Use case 1. There could be a problem for the naming of task plugins. For example, we both have `emr` related stuff in AWS and Alibaba Cloud. 2. It will be hard for ds users to keep code updated with the community. Users working in big companies may have their customzied versions of task plugins. When community releases a new ds version, users will probably have a lot of trouble trying to rebase the branch. There could be tons of file conflicts to be dealt with. 3. As more and more developers engage in the ds community, the number of task plugins will increase explosively. Many of the task plugins in the future may not be necessary for all users. For the scenarios 1 and 2 listed above, I think we might classify task plugins into basic plugins and provider-related plugins, put them into separate directory and manage them differently. For 3, If there's a mechanism for users to decide which plugins to install and which not to, it will definitely be better. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
