You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/11/22 07:52:38 UTC
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #12967: [Bug] startParams Not in effect
github-actions[bot] commented on issue #12967:
URL: https://github.com/apache/dolphinscheduler/issues/12967#issuecomment-1323249579
### 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
![image](https://user-images.githubusercontent.com/71861187/203256068-bbf06d93-61b0-4aa9-a28e-d43f6ba67164.png)
![image](https://user-images.githubusercontent.com/71861187/203256084-795e4c65-a98d-4d90-8bf5-a773a5ad3b2d.png)
![image](https://user-images.githubusercontent.com/71861187/203256179-528427ad-6268-44ec-8ba3-ac329007d13f.png)
The startup parameter is set, but it does not take effect
### What you expected to happen
The startup parameters take effect
### How to reproduce
Add a spark workflow, the main program parameter defines the ${} variable, and the startup parameter sets the value of the variable when it is executed once
### Anything else
_No response_
### Version
2.0.x
### 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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org