[GitHub] [dolphinscheduler] cheneychoi opened a new issue #7887: [Bug] [Parameter Context] The preparameter OUT is null

Fri, 07 Jan 2022 06:33:41 -0800 


cheneychoi opened a new issue #7887:
URL: https://github.com/apache/dolphinscheduler/issues/7887


   ### 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
   
   在首节点设定两个OUT参数，其中一个给常量，另一个以shell设置参数值传递的方式，传递到下一个节点时，其中常量的参数为null
   
![image](https://user-images.githubusercontent.com/23023197/148558082-d585afef-fa4c-43f7-a746-67c3fc90fd3b.png)
   
![image](https://user-images.githubusercontent.com/23023197/148558172-974f8199-704b-4b8d-ba6a-a647f2f1d167.png)
   
![image](https://user-images.githubusercontent.com/23023197/148558219-e7c08f89-f3ee-49ff-8cb9-0a6edfa78ebb.png)
   
   
   ### What you expected to happen
   
   AbstractParameters中在给OUT参数设置value时，把原有的常量值设置了为null
   
   ### How to reproduce
   
   
![image](https://user-images.githubusercontent.com/23023197/148558549-ca1d24d9-5b4e-4a9e-a487-73da75be45f7.png)
   
![image](https://user-images.githubusercontent.com/23023197/148558600-e89bc08a-c983-447f-81ab-6e69d0a72121.png)
   
![image](https://user-images.githubusercontent.com/23023197/148558645-71e60c1f-c3bc-4fa7-95d1-e2c99a5f8bf9.png)
   
![image](https://user-images.githubusercontent.com/23023197/148558700-f5aa7d25-325b-4565-8fb4-b5ad24769617.png)
   
   
   ### Anything else
   
   每次都会发生
   
   ### Version
   
   2.0.1
   
   ### Are you willing to submit 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: [email protected]

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

Reply via email to