Hi Dev Team
The scheme of The global params that Task need change as blow。 Here is the ISSUE about this DISCUSS。 https://github.com/apache/dolphinscheduler/issues/5565 I will 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. 1. 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. 1. 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 If you have some question or have the better plan ,please contact me .thank you. 如果您错误接收了该邮件，请通过电子邮件立即通知我们。请回复邮件到 [email protected]，即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to [email protected] ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.
