wangxj3 opened a new pull request #5603:
URL: https://github.com/apache/dolphinscheduler/pull/5603


   This pr change the scheme of global param that depend on the relation of the 
task.
   Here is the detail about this .
   1.   create taskInstance
   Get the previous tasks ,get the varPool of those tasks, put those into this 
varPool. If the previous task has the same varPool name,use the value that is 
not null.If all of the  values  are null, use the earlier one.
   2.   Worker get the param
   Master will send the varPool to the Worker ,and taskPorcessor get the 
varPool with the format of List<Property>, varPool will do the same as the 
localParam.
   3.   Worker response out Parm
   When the user define the OUT param in the page of Task Definition.Worker 
will get the result of Processor .
   The different Processor return the different format ,for example SQL return 
the format of List<Map<String,String>>,users could get more than one line or 
more than one column;SHELL get the Map<String,String> or String.This out Param 
will add into the varPool ,and send to the Master ,save into the databases.Also 
,this value will save into the localParam
   


-- 
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]


Reply via email to