You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "Orange-Summer (via GitHub)" <gi...@apache.org> on 2023/07/13 16:31:15 UTC

[GitHub] [dolphinscheduler] Orange-Summer opened a new issue, #14545: [Feature][Master][UI] Cross-workflow parameter passing

Orange-Summer opened a new issue, #14545:
URL: https://github.com/apache/dolphinscheduler/issues/14545

   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Description
   
   In the subprocess task, the subworkflow can choose its own output parameters to output to the downstream tasks in the parent workflow.
   This is a [DolphinScheduler project of OSPP-2023.](https://summer-ospp.ac.cn/org/prodetail/232290357)
   
   ### Use case
   
   Example:
   This is the output parameter of the task in the subworkflow
   ![image](https://github.com/apache/dolphinscheduler/assets/61171207/336ed038-1353-496a-8016-1b13722bab81)
   This is the output parameter defined in the subworkflow
   ![image](https://github.com/apache/dolphinscheduler/assets/61171207/b1dff352-8628-4014-b021-6a8c70ee2b1b)
   Output parameter1 and parameter2 in the downstream task of the subworkflow task, and finally output parameter1 successfully
   ![image](https://github.com/apache/dolphinscheduler/assets/61171207/6a97f435-e9a9-434b-8312-44dc9db82674)
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [dolphinscheduler] SbloodyS closed issue #14545: [Feature][Master][UI] Cross-workflow parameter passing

Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS closed issue #14545: [Feature][Master][UI] Cross-workflow parameter passing
URL: https://github.com/apache/dolphinscheduler/issues/14545


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [dolphinscheduler] Orange-Summer commented on issue #14545: [Feature][Master][UI] Cross-workflow parameter passing

Posted by "Orange-Summer (via GitHub)" <gi...@apache.org>.
Orange-Summer commented on issue #14545:
URL: https://github.com/apache/dolphinscheduler/issues/14545#issuecomment-1634554784

   Design doc:
   
   Modify the `submitPostNode` method in the `WorkflowExecuteRunnable` class so that the last node in the subworkflow outputs the correct parameters to the varpool of the workflow, which is finally passed to the subworkflow task in the parent workflow.
   
   In the `WorkflowExecuteThreadPool` class, the `notifyProcessChanged` method is used to change the subworkflow to the parent workflow, and obtains all the parent workflows and corresponding subworkflow tasks. Add a method here to assign the varpool of the subworkflow to the varpool in the `SubProcessParameters` of the subworkflow task, and the code for passing parameters to downstream tasks has been implemented.


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org