[Fix-17639] Parameter passing docs improvement #17660
Open
+32
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for opening this pull request! Please check out our contributing guidelines. (https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/contribute/join/pull-request.md) |
SbloodyS
reviewed
Nov 10, 2025
| > | ||
| > **1.参数传递的行为在3.3.x版本中发生了变化** | ||
| > | ||
| > 在旧版本3.2.x中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X； |
Member
There was a problem hiding this comment.
Suggested change
| > 在旧版本3.2.x中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X； | |
| > 在旧版本低于3.2.2中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X； |
| > | ||
| > In older version 3.2.x, downstream node B could obtain the out type output X of upstream node A without configuring an IN type local variable X. | ||
| > | ||
| > In the new version 3.3.x, 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. |
Member
There was a problem hiding this comment.
Suggested change
| > In the new version 3.3.x, 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. | |
| > 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. |
…re the usage of parameter passing in the documentation has been changed.
Co-authored-by: xiangzihao <[email protected]>
Co-authored-by: xiangzihao <[email protected]>
e7e7b11 to
413a015
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 3.3.x has modified the behavior of parameter passing, therefore the usage of parameter passing in the documentation has been changed.
Purpose of the pull request
Version 3.3.x has modified the behavior of parameter passing, therefore the usage of parameter passing in the documentation has been changed.
In this update, I submitted a documentation update regarding changes to parameter passing usage to fix #17639
Brief change log
The example images and instructions for parameter passing in the document have been modified.
Verify this pull request
This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(or)
Pull Request Notice
Pull Request Notice
If your pull request contains incompatible change, you should also add it to
docs/docs/en/guide/upgrade/incompatible.md