honkerjha opened a new issue, #17967:
URL: https://github.com/apache/dolphinscheduler/issues/17967

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   I first tested with two Shell nodes:
   In node1, I set an output parameter as a custom parameter with direction 
out, and executed echo '${setValue(output=123)}' in the script to assign a 
value to it.
   In node2, I executed echo ${output} and set node1 as its upstream task.
   when I added a custom parameter named output (direction in) to node2, node2 
could print the parameter value normally.
   However, it could NOT retrieve the output value when I modified node1 to a 
Stored Procedure node.
   I set output as the output value of the upstream Stored Procedure node 
(node1).it could NOT retrieve the output value.
   
   Node1 configuration:
   <img width="203" height="243" alt="Image" 
src="https://github.com/user-attachments/assets/7a1db334-ef15-49c8-84f5-df4bd5c99f1f";
 />
   
   Node2 configuration
   <img width="242" height="255" alt="Image" 
src="https://github.com/user-attachments/assets/9ee6dea7-de3b-4391-b9a6-511d14b32c89";
 />
   
   It seems node1 successfully retrieved the return value: return123.
   <img width="415" height="175" alt="Image" 
src="https://github.com/user-attachments/assets/b27d59de-cec3-45e4-8b25-74056a7c19b7";
 />
   
   But node2 output was empty.
   <img width="242" height="113" alt="Image" 
src="https://github.com/user-attachments/assets/3250790f-7733-4ade-90f0-d00d42ca7460";
 />
   
   I tested the exact same operations in version 3.2.2, and there were NO such 
issues.
   
   I followed the parameter passing section in the official documentation for 
version 3.4.0, so the syntax should be correct.
   
   
   
   ### What you expected to happen
   
   Local parameter passing of Procedure to Shell not working in version 3.4.0
   It seems node1 successfully retrieved the return value: return123.
   <img width="415" height="175" alt="Image" 
src="https://github.com/user-attachments/assets/51141cdf-811f-4787-b4a4-91bf391b8a9e";
 />
   But node2 output was empty.
   <img width="242" height="113" alt="Image" 
src="https://github.com/user-attachments/assets/52a2cd49-651d-48b2-aaef-bf9415dbf5c4";
 />
   
   ### How to reproduce
   
   Node1 configuration
   
   <img width="203" height="243" alt="Image" 
src="https://github.com/user-attachments/assets/57644a93-e736-4fd8-b8db-ad8ee68518b2";
 />
   
   Node2 configuration
   
   <img width="242" height="255" alt="Image" 
src="https://github.com/user-attachments/assets/807e6b46-18b1-475a-aa80-0e8b7dc2003e";
 />
   
   Node1  return value
   
   <img width="415" height="175" alt="Image" 
src="https://github.com/user-attachments/assets/cf89b44d-90e8-459b-95ef-6d9d359f0af7";
 />
   
   node2 output
   
   <img width="242" height="113" alt="Image" 
src="https://github.com/user-attachments/assets/c918b529-0c79-4a29-a793-c0d045d6dd89";
 />
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.4.0
   
   ### Are you willing to submit PR?
   
   - [ ] 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: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to