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

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   When creating a new MySQL data source, I need to copy the MySQL data source 
JAR file to the following directories: `api-server/libs`, `alert-server/libs`, 
`master-server/libs`, `worker-server/libs`, and `tools/libs`. Currently, I can 
only achieve this by modifying the YAML files in the `helm/templates` folder.
   
   ```yaml        
       command:
               - sh
               - -c
               - |
                 sed -i 
's|$DOLPHINSCHEDULER_HOME/libs/\*|$DOLPHINSCHEDULER_HOME/libs/\*":"$CLASSPATH_API|g'
 /opt/dolphinscheduler/bin/start.sh;
                 exec /opt/dolphinscheduler/bin/start.sh
   ```
   Additionally, after replacing the code as described, I need to configure the 
`classpath_api` environment variable externally to load the MySQL driver from 
`common.sharedStoragePersistence`. This method is extremely cumbersome.
   
   
   
   
   
   It would be better to provide a Persistent Volume Claim (PVC) to load 
external JAR files. Ideally, there should be a separate external JAR loading 
path for each component: `api-server`, `alert-server`, `master-server`, 
`worker-server`, and `tools`. This would allow external users to easily provide 
these JAR files to DolphinScheduler.
   
   
   
   
   
   
   
   
   
   
   ### Are you willing to submit a 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