Mighten opened a new pull request, #16933:
URL: https://github.com/apache/dolphinscheduler/pull/16933

   <!--Thanks very much for contributing to Apache DolphinScheduler, we are 
happy that you want to help us improve DolphinScheduler! -->
   
   ## Purpose of the pull request
   
   This Pull Request fixes a bug that prevents passing the `varPool` to the 
next Shell Node and aims to close #16540.
   - [ ] #16540 
   
   ## Brief change log
   - Updated the `TaskExecutionContext` with the `varPool` in JSON format after 
executing the Shell node.
   
   ## Verify this pull request
   
   This change can be verified as follows:
   
   1) Setup a *shell-node-to-shell-node* workflow as follows:
   
![workflow-definition](https://github.com/user-attachments/assets/acbe237b-98b8-4449-b785-e62501da2754)
   
   2) Bring workflow online and start it:
   
   3) Check for Worker log in IntelliJ IDEA Console:
   
   
![after-fixed-result-console](https://github.com/user-attachments/assets/1546ff84-024a-45dd-8727-8b45b5e43f76)
   
   "After this PR, the `a` and `b` in the `varPool` can be substituted 
correctly.
   
   > Before this PR, the `a` and `b` in the `varPool` cannot be found:
   > 
![before-1-not-updated](https://github.com/user-attachments/assets/d187e8d3-3a23-46fc-b95f-428f22c38b2b)
   
   
   4) Check for Workflow Instance DB items with SQL:
   
   
![workflow-instance-db](https://github.com/user-attachments/assets/b54e5d1f-d418-4b87-9180-f1cf6c35a9d7)
   - record with id 58 is before this PR, the varPool is NOT properly updated.
   - record with id 57 is after this PR, the varPool is properly updated.
   
   ## Pull Request Notice
   [Pull Request 
Notice](https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/contribute/join/pull-request.md)
   
   If your pull request contain incompatible change, you should also add it to 
`docs/docs/en/guide/upgrede/incompatible.md`
   


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