jon-qj commented on issue #5925: URL: https://github.com/apache/dolphinscheduler/issues/5925#issuecomment-891684920
> **About migrating to DolphinScheduler** > > It is believed that many users are attracted by the functions of DS, but not everyone can easily migrate the original scheduling configuration to DS, especially the scheduling platform with thousands of jobs such as data warehouse. > > Most users really need a tool for easy data migration, and I am one of them, and I need to migrate more than 6000 jobs. > > So after reading most of the code, I wrote a simple script, which can directly generate the job information of batch configuration into the database. Of course, I will continue to migrate my flows in Azkaban to DS: > > * https://github.com/reele/process_definition_import_tool > > **Therefore, is it necessary to add a common template import interface in DS, so that the data of other scheduling platforms can be formatted and exported, and then directly imported into DS? Or implement a common stand-alone tool for data conversion?** > > ## **Which version of DolphinScheduler:** > -[1.3.6-release] In my opinion, this function is generally implemented by users themselves. There are too many scheduling platforms (including self-development), complex structures and more uncertainties, which makes it difficult to parse and initialize into DS general format (especially on front-end, how to initialize location to define the coordinates of each task?), we can collect the user's own scripts, summarize them to the tool set on the DS official website, and download and modify them by ourselves. -- 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]
