liqingwang commented on issue #10103: URL: https://github.com/apache/dolphinscheduler/issues/10103#issuecomment-1131238019
Hi @zwZjut, I don't think we need to ```SPRING_DATASOURCE_DRIVER_CLASS_NAME```. Here is the reason. You can see [this](https://github.com/apache/dolphinscheduler/blob/3.0.0-alpha-release/deploy/kubernetes/dolphinscheduler/templates/_helpers.tpl#L123) define the ```DATABASE``` And when you build the Docker image, will run the ```./bin/start.sh``` on Api || Matset || Worker || Alert-Server. The ```./bin/start.sh``` will source ```$DOLPHINSCHEDULER_HOME/conf/dolphinscheduler_env.sh``` And ```dolphinscheduler_env.sh``` will set the ```SPRING_PROFILES_ACTIVE``` , you can see the code [here](https://github.com/apache/dolphinscheduler/blob/3.0.0-alpha-release/script/env/dolphinscheduler_env.sh#L32) Then you can see the ```driver-class-name``` will be chosen from the different data sources. [postgresql](https://github.com/apache/dolphinscheduler/blob/3.0.0-alpha-release/dolphinscheduler-api/src/main/resources/application.yaml#L45) and [mysql](https://github.com/apache/dolphinscheduler/blob/3.0.0-alpha-release/dolphinscheduler-api/src/main/resources/application.yaml#L139) -- 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]
