Mrhs121 commented on issue #17639: URL: https://github.com/apache/dolphinscheduler/issues/17639#issuecomment-3483656102
> Oh, i get you!in this way ,i can get the variable from the upstream node,but i have to explicitly add IN type variables every time,it seems a bit trouble. Why can't I declare the OUT type variable first and then add it to the local variables so that downstream nodes can use it directly?That's how it's demonstrated in the official documentation. Or could it be optimized by allowing selection of an existing local variable from a dropdown menu? I found that the behavior of Parameter passing has changed in version 3.3.x. In old version 3.2.x, as shown in the above example, task2 can obtain the upstream output without configuring a variable of type in. On the contrary, when a variable of type in is set, the upstream output cannot be obtained. In version 3.3.x, the following processing logic has been added. For example, in the above example, only when local var ```task_type``` is configured in task2 will the upstream ```varPools``` value(internal_table_creation_task) be used to override local param ```task_type``` https://github.com/apache/dolphinscheduler/blob/797014807f774ff17f617db13b9e6acd64164f6b/dolphinscheduler-service/src/main/java/org/apache/dolphinscheduler/service/expand/CuringParamsServiceImpl.java#L226-L235 -- 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]
