Radeity commented on PR #12930: URL: https://github.com/apache/dolphinscheduler/pull/12930#issuecomment-1336178784
> What I'm concerned about is whether there is a possibility the user does not intend to update the parameter but mistakenly create a parameter with a duplicate key and this change will override the parameter? Hi @EricGao888, you're right, it's possible. However, current priority is `Local Parameter > Parameter Context > Global Parameter`, there's a possibility that override global parameter by setting output parameter, either. I think users themselves should be responsible for preventing mistakes, we just have to declare clearly how DS deals with this situations. Like some other declaration in doc now: > In the case of upstream tasks can pass parameters to the downstream, there may be multiple tasks upstream that pass the same parameter name: > > - Downstream nodes prefer to use parameters with non-empty values > - If there are multiple parameters with non-empty values, select the value from the upstream task with the earliest completion time -- 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]
