SbloodyS commented on code in PR #17660: URL: https://github.com/apache/dolphinscheduler/pull/17660#discussion_r2509177351
########## docs/docs/en/guide/parameter/context.md: ########## @@ -23,7 +23,17 @@ The value of upstream parameter can be updated in downstream node in the same wa Upstream parameter will be override when defining parameter with the same name in downstream node. -> Note: If there are no dependencies between nodes, local parameters cannot be passed upstream. +> Note: +> +>**1. Parameter passing behavior has changed in version 3.3.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. Review Comment: ```suggestion > In older version before 3.2.2, downstream node B could obtain the out type output X of upstream node A without configuring an IN type local variable X. ``` ########## docs/docs/en/guide/parameter/context.md: ########## @@ -23,7 +23,17 @@ The value of upstream parameter can be updated in downstream node in the same wa Upstream parameter will be override when defining parameter with the same name in downstream node. -> Note: If there are no dependencies between nodes, local parameters cannot be passed upstream. +> Note: +> +>**1. Parameter passing behavior has changed in version 3.3.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. Review Comment: ```suggestion > 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. ``` ########## docs/docs/zh/guide/parameter/context.md: ########## @@ -23,7 +23,19 @@ DolphinScheduler 允许在任务间进行参数传递，目前传递方向仅支 如果定义了同名的传递参数，上游节点的参数将被覆盖。 -> 注：若节点之间没有依赖关系，则局部参数无法通过上游传递。 +> 注: +> +> **1.参数传递的行为在3.3.x版本中发生了变化** +> +> 在旧版本3.2.x中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X； +> +> 在新版本3.3.x中修改领了局部变量的获取逻辑：只有下游节点B配置了IN类型的局部变量X，才可使用上游节点A的out类型输出X。 Review Comment: ```suggestion > 在新版本高于3.3.0中修改领了局部变量的获取逻辑：只有下游节点B配置了IN类型的局部变量X，才可使用上游节点A的out类型输出X。 ``` ########## docs/docs/zh/guide/parameter/context.md: ########## @@ -23,7 +23,19 @@ DolphinScheduler 允许在任务间进行参数传递，目前传递方向仅支 如果定义了同名的传递参数，上游节点的参数将被覆盖。 -> 注：若节点之间没有依赖关系，则局部参数无法通过上游传递。 +> 注: +> +> **1.参数传递的行为在3.3.x版本中发生了变化** +> +> 在旧版本3.2.x中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X； Review Comment: ```suggestion > 在旧版本低于3.2.2中，下游节点B无需配置IN类型局部变量X即可获取上游节点A的out类型输出X； ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
