flink on yarn execute fail

[ljl568419709]

Search before asking

• [X] I had searched in the issues and found no similar issues.

What happened

Provider org.apache.seatunnel.connectors.seatunnel.jdbc.source.JdbcSource not a subtype 而且seatunnel提交到yarn时，seatunnel并没有将connectors/seatunnel提交到yarn，很定是提交不成功的，详情看下图

SeaTunnel Version

seatunall 2.3.3

SeaTunnel Config

./bin/start-seatunnel-flink-13-connector-v2.sh -e run-application --master yarn-application --config /apps/hive/apache-seatunnel-2.3.3/config/v2.batch.config.mysql_mysql.template

Running Command

env {
parallelism = 4
job.mode = "BATCH"
}
source{
jdbc {
url = "jdbc:mysql://10.26.32.16:3306/communal_new?serverTimezone=GMT%2b8&useUnicode=true&characterEncoding=UTF-8&rewriteBatchedStatements=true"
driver = "com.mysql.cj.jdbc.Driver"
connection_check_timeout_sec = 100
user = "root"
password = "Meicloud12#$"
query = "select * from sys_menu"
}
}

transform {
# If you would like to get more information about how to configure seatunnel and see full list of transform plugins,
# please go to https://seatunnel.apache.org/docs/transform-v2/sql
}

sink {
jdbc {
url = "jdbc:mysql://10.26.32.16:3306/test"
driver = "com.mysql.cj.jdbc.Driver"
user = "root"
password = "Meicloud12#$"
# Automatically generate sql statements based on database table names
generate_sink_sql = true
database = test
table = sys_menu
}
}

Error Exception

Provider org.apache.seatunnel.connectors.seatunnel.jdbc.source.JdbcSource not a subtype

Zeta or Flink or Spark Version

No response

Java or Scala Version

flink 1.3.6 jdk 1.8 scala 2.1

Screenshots

No response

Are you willing to submit PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.