khadgarmage edited a comment on issue #201: Task plug-in research, out of 
solution(任务插件化调研,出解决方案)
URL: 
https://github.com/apache/incubator-dolphinscheduler/issues/201#issuecomment-545028146
 
 
   
   @gaojun2048 +1, I agree with your design. I also think of a few additional 
points here:
   1. Task plug-in development, there are two points to consider, one is a 
plug-in that allows users to directly develop their own business needs, and the 
use is more flexible; the other is to allow open source enthusiasts to develop 
third-party plug-ins, so that will promote the development of dolphinscheduler, 
ideas are more divergent, is there a plug-in market? Therefore, based on the 
function of the custom task plug-in, it is necessary to support the third-party 
plug-in import. After the import and the custom task plug-in is a process, the 
workload itself is not large, but the import is added on the basis of the 
original.
   2. Plug-in development does not depend on java, can be any language, 
executable program, the scheduling platform does is transparent transmission 
parameters, execution and scheduling. Developers can have more choices. For 
example, a shell script can be packaged into a plugin using some parameters. 
For example, someone can write an executable file in golang, define some 
parameters, to make a plugin.
   3. System upgrade or migration is also a point to note, to ensure that the 
plug-in will still take effect after migration or upgrade.
   -----
   @gaojun2048 +1 很赞同你的需求,我这边还想到几个补充的点:
   
1、任务插件化开发,可以有两点考虑,一个是让使用者直接可以开发自己业务需求的插件,使用上更加灵活;另一个是可以让开源爱好者开发第三方插件,这样对ds更是一种正向的推动,思路更发散点,是不是可以有插件market。
   所以在自定义任务插件的功能基础上,要支持第三方插件导入,导入后和自定义任务插件是一个流程,这个工作量本身并不大,只是在原来的基础上增加了导入。
   2、自定义任务插件,可以不局限于jar包,可以是shell, python, 
也可以是一个可执行文件,可以有更多的选择。比如说一个shell脚本使用一些参数,就可以封装成一个插件;同时也可以用golang写一个可执行文件,传到服务器,定义一些入参,也可以作为一个插件。
   3、系统升级或者迁移也是个要注意的点,要保证迁移或者升级后,插件依然能够生效。

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to