-
Notifications
You must be signed in to change notification settings - Fork 5k
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
1, Create a workflow where Node A is configured with an OUT parameter param1 set to 333, and Node B is configured with an IN parameter param1 set to 111

2, Run this workflow,
Node A log:
Node B log:
3, The official documentation specifies the following parameter precedence:
As there are multiple sources of the parameter value, it will raise parameter priority issues when the parameter name is the same. The priority of DolphinScheduler parameters from high to low is:
Startup Parameter > Local Parameter > Parameter Context > Global Parameter > Project-level Parameter.
Howerver, Node B log : The value of param1 is 333, not 11111.
What you expected to happen
If Local Parameter > Parameter Context, the value of param1 should be 11111
How to reproduce
1, Create a workflow where Node A is configured with an OUT parameter param1 set to 333, and Node B is configured with an IN parameter param1 set to 111

2, Run this workflow,
Anything else
No response
Version
dev
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct