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

   ### 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
   
   When we start a job in a Complement Data situation, extended built-in 
parameters like '$[yyyy-MM-dd]' defined in shell task scripts do not work when 
the task does not set any parameters.
   
   
![1](https://github.com/apache/dolphinscheduler/assets/119404633/078d1c82-33fd-4772-9876-9e5f832faba9)
   
![2](https://github.com/apache/dolphinscheduler/assets/119404633/1ceb5caa-2c08-4f2c-b3df-bf0ff830c214)
   
![3](https://github.com/apache/dolphinscheduler/assets/119404633/8a810ac1-b413-433b-967a-991bbc8bc61f)
   
   
   ### What you expected to happen
   
   We expect to return the scheduling time2024-02-01, but the result is the 
system time2024-03-14.
   
   
   ### How to reproduce
   
   In version 3.1.9, the CuringGlobalParams class in the master node returns 
null when building task parameters, as globalParams, localParams, and varParams 
are all empty. This results in the system.datetime variable not being populated 
into the context.
   
![4](https://github.com/apache/dolphinscheduler/assets/119404633/1b789f21-7a8a-4eb2-8093-6ba33d16b175)
   
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.1.x
   
   ### 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