You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/07/26 03:06:45 UTC

[GitHub] [dolphinscheduler] ruanwenjun commented on pull request #11137: Add base loop task execotor and http template parser

ruanwenjun commented on PR #11137:
URL: https://github.com/apache/dolphinscheduler/pull/11137#issuecomment-1194940673

   > I have three small points:
   > 
   > 1. The use of the mode is slightly complicated, requiring a third-party platform to provide an interface without user authentication
   
   In fact, there exist these kinds of tasks, ds is as a scheduler trigger to submit tasks to these platforms.
   
   > 2. If the number of tasks is large, it may slow down the performance of the worker.
   Yes, we can use single thread pool to loop the status in the future, but I think this will not heavier than process.
   
   > 3. When starting a workflow, a unique ID is returned as the ID of the workflow instance, third-party platform use the instance ID to query  status of workflow instance and tasks.
   
   Third-party platform can call API-Server to query the status, this PR is used to provide a base task for `query status task` like EMR. 
   
   
   


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org