EricGao888 commented on issue #9675: URL: https://github.com/apache/dolphinscheduler/issues/9675#issuecomment-1107837080
> > In fact, we can unite `dolphinscheduler_env.sh` into one. > > Another question is, we already have > > https://github.com/apache/dolphinscheduler/blob/ebc4253d5020c0bf319561985c0c25bace5c283b/dolphinscheduler-tools/src/main/resources/application.yaml#L20-L24 > > to config db connection, why we need to config again in `dolphinscheduler_env.sh`? Could we remove duplicate db connection configuration in `dolphinscheduler_env.sh`? Okay, I think I got it. DS has been refactored in micro-services fashion. Every module has its own `{module_name}/conf/application.yaml` after building the project. Therefore, it is definitely more reasonable for users to config `bin/env/dolphinscheduler_env.sh` so that the configuration will take effect globally. -- 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]
