[Bug] [subprocess] params passing over subprocess(subworkflow) is null
Search before asking
- [x] I had searched in the issues and found no similar issues.
What happened
variables passing to subprocess's child node is null.
What you expected to happen
variables passing to subprocess's child node is not null.
How to reproduce
reproduce like https://dolphinscheduler.apache.org/zh-cn/docs/3.2.2/guide/parameter/context on "SubProcess 任务传递参数"
1, workflow1:subprocess_example1
-
subprocess_example1 has 1 shell task node.
-
task node script content
echo '${setValue(var1=1234)}'
echo '${setValue(var2=5678)}'
- task node self-defined params
var1 out varchar
var2 out varchar
- workflow's global params
var1 out
var2 out
2, workflow2:subprocess_example2
- subprocess node: B
- B's child node C node C script content(shell node):
echo "var1=${var1}"
echo "var2=${var2}"
result
var1 and var2 are all null.
Anything else
No response
Version
3.2.2
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Search before asking
- [x] I had searched in the issues and found no similar issues.
What happened
variables passing to subprocess's child node is null.
What you expected to happen
variables passing to subprocess's child node is not null.
How to reproduce
reproduce like https://dolphinscheduler.apache.org/zh-cn/docs/3.2.2/guide/parameter/context on "SubProcess 任务传递参数"
1, workflow1:subprocess_example1
-
subprocess_example1 has 1 shell task node.
-
task node script content
echo '${setValue(var1=1234)}'
echo '${setValue(var2=5678)}'
- task node self-defined params
var1 out varchar
var2 out varchar
- workflow's global params
var1 out
var2 out
2, workflow2:subprocess_example2
- subprocess node: B
- B's child node C node C script content:
echo "var1=${var1}"
echo "var2=${var2}"
result
var1 and var2 are all null.
Anything else
No response
Version
dev
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
There has 2 problems: 1, produce varariables node, prepareParamsMap build wrong
2, varariables pool does not passing to subprocess node.
already fixed by myself
There has 2 problems: 1, produce varariables node, prepareParamsMap build wrong
2, varariables pool does not passing to subprocess node.
already fixed by myself
There has 2 problems: 1, produce varariables node, prepareParamsMap build wrong 2, varariables pool does not passing to subprocess node.
I remember this should be fixed on dev.
already fixed by myself
There has 2 problems: 1, produce varariables node, prepareParamsMap build wrong 2, varariables pool does not passing to subprocess node.
I remember this should be fixed on dev.
OK, I will compare between dev and 3.2.2, and fixed it on dev, at present, I use on 3.2.2.
already fixed by myself
There has 2 problems: 1, produce varariables node, prepareParamsMap build wrong 2, varariables pool does not passing to subprocess node.
I remember this should be fixed on dev.
OK, I will compare between dev and 3.2.2, and fixed it on dev, at present, I use on 3.2.2.
3.2.2 May not be suitable for use in production :sad
3.2.2 May not be suitable for use in production :sad
why? :sad
3.2.2 May not be suitable for use in production :sad
why? :sad
It has not yet been verified on a large scale in a production environment, and some users have reported bugs.