Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [dolphinscheduler-api] The global parameters of the sub_process node are not passed to the associated workflow task #7962

Closed
2 of 3 tasks
janeHe13 opened this issue Jan 12, 2022 · 3 comments · Fixed by #7973
Assignees
Labels
bug Something isn't working release cherry-pick Mark this issue/PR had cherry-pick for release version
Milestone

Comments

@janeHe13
Copy link
Contributor

janeHe13 commented Jan 12, 2022

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

  1. Create workflow A and the task is shell_ 1. Global parameter setting id = 1

image

image
2. Sub node B is associated with workflow A
image
3. set id = 3 of the global parameter for the Sub node B , Run Sub node B, shell_1'id is 1, should be 3
image

What you expected to happen

.

How to reproduce

.

Anything else

No response

Version

2.0.2

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@janeHe13 janeHe13 added bug Something isn't working Waiting for reply Waiting for reply labels Jan 12, 2022
@github-actions
Copy link

Hi:

@caishunfeng caishunfeng added this to the 2.0.3-release milestone Jan 12, 2022
@janeHe13 janeHe13 changed the title [Bug] [dolphinscheduler-api] After the sub_process node is associated with task, the global parameters read by task a are the values of the last run [Bug] [dolphinscheduler-api] The global parameters of the sub_process node are not passed to the associated workflow task Jan 12, 2022
@lenboo
Copy link
Contributor

lenboo commented Jan 12, 2022

@ruanwenjun Hello wenjun, can you solve this problem?

@ruanwenjun
Copy link
Member

@janeHe13 Thanks for your feedback, this is a bug. I have submitted a pr to fix in dev branch #7969.
And this will be released in 2.0.3.

@caishunfeng caishunfeng added the release cherry-pick Mark this issue/PR had cherry-pick for release version label Jan 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release cherry-pick Mark this issue/PR had cherry-pick for release version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants