The MySQL-type data source is using a DolphinDB-type driver. #18023
njnu-seafish
started this conversation in
Show and tell
Replies: 3 comments
|
In the DolphinScheduler runtime environment (Worker nodes), both the DolphinDB JDBC driver JAR and the MySQL JDBC driver JAR are present; however, the class loading mechanism causes the DolphinDB driver to be registered first. After removing the DolphinDB JDBC driver JAR, the program use the MySQL JDBC driver. |
0 replies
|
This is because we currently haven't specified a driver when creating the connection. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ds version: 3.3.1-release
1, Create a SQL task using MySQL-type datasource

2, Run this task, The following error log will appear.
3,Find the jar about com.dolphindb.jdbc.Driver
4, Remove the jar, the restart the worker service
$ ll ./plugins/task-plugins/ | grep -i dolphinscheduler-task-aliyunserverlessspark
-rw-r--r-- 1 dolphinscheduler dolphinscheduler 265M Feb 18 2022 dolphinscheduler-task-aliyunserverlessspark-3.3.2-SNAPSHOT-shade.jar_bak0305
systemctl restart dolphinscheduler-worker
5, Run this task again, it is ok
6, Change the datasource with error password, run again
All reactions