You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "njnu-seafish (via GitHub)" <gi...@apache.org> on 2026/03/10 06:27:17 UTC

[I] [Doc][Parameter Context] Improvement Parameter passing behavior doc [dolphinscheduler]

njnu-seafish opened a new issue, #18045:
URL: https://github.com/apache/dolphinscheduler/issues/18045

   ### 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
   
   > 1. Parameter passing behavior has changed in version 3.3.x**
   In the new version after 3.3.0, the logic for obtaining local variables has been modified: downstream node B can only use the out type output X of upstream node A if it has configured an IN type local variable X.
   
   Howerver,Exception for Switch Tasks: Since Switch tasks lack an interface for custom parameters, they can consume upstream OUT variables without explicit IN variable mapping.
   
   ### Documentation Links
   
   https://dolphinscheduler.apache.org/zh-cn/docs/3.4.1/guide/parameter/context
   
   ### 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


Re: [I] [Doc][Parameter Context] Improvement Parameter passing behavior doc [dolphinscheduler]

Posted by "SbloodyS (via GitHub)" <gi...@apache.org>.
SbloodyS closed issue #18045: [Doc][Parameter Context] Improvement Parameter passing behavior doc
URL: https://github.com/apache/dolphinscheduler/issues/18045


-- 
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


Re: [I] [Doc][Parameter Context] Improvement Parameter passing behavior doc [dolphinscheduler]

Posted by "njnu-seafish (via GitHub)" <gi...@apache.org>.
njnu-seafish commented on issue #18045:
URL: https://github.com/apache/dolphinscheduler/issues/18045#issuecomment-4029147598

   1, Create a workflow where Node A is configured with an OUT parameter param1 set to 111, and Node B is a Switch task without configuring an IN parameter
   
   <img width="1617" height="629" alt="Image" src="https://github.com/user-attachments/assets/088d0a80-fb84-4f9a-9619-dc07103865f9" />
   
   <img width="1173" height="797" alt="Image" src="https://github.com/user-attachments/assets/02416331-3f4f-47fb-a2ab-a16b7a25fd1a" />
   
   <img width="1217" height="1202" alt="Image" src="https://github.com/user-attachments/assets/d122aeb5-dc8f-461c-888d-518cbcef8ec4" />
   
   
   2, Unlike other task types, Switch tasks do not require the definition of an IN-type local variable X to retrieve the OUT-type output X from an upstream node. This is because the Switch task type does not support the configuration of custom parameters.
   
   <img width="1545" height="574" alt="Image" src="https://github.com/user-attachments/assets/0f202820-3bf8-4c57-a0ad-0b5b37c2997a" />
   


-- 
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