[
https://issues.apache.org/jira/browse/FLINK-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16933:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> No suitable driver found for jdbc:xxx
> -------------------------------------
>
> Key: FLINK-16933
> URL: https://issues.apache.org/jira/browse/FLINK-16933
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.9.0
> Environment: CentOS Linux release 7.7.1908 (Core)
> Reporter: morgan
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> For example, there are two streaming jobs A and B.
> When A calculation is running, I submit B, at this time, an exception will be
> thrown, Caused by: java.sql.SQLException: No suitable driver found for jdbc:
> clickhouse: // host: 8123 / data. When stopping flink ./stop-cluster.sh. Then
> restart ./start-cluster.sh. When flink is not running any tasks, submit B,
> and B is successfully executed. But if you execute B multiple times, Caused
> by: java.sql.SQLException: No suitable driver found for jdbc: clickhouse: //
> host: 8123 / data will also be thrown. Both B and A depend on clickhouse4j in
> the common. A submission can run normally, but B can only be executed when
> restart and flink does not contain other tasks, which seems strange. I
> checked flink / lib / and clickhouse4j-1.4.1.jar has been added. I tried to
> package clickhouse4j-1.4.1.jar into the job, but still couldn't solve this
> problem. I tried to add it to jre / lib / ext and added it to the classpath.
> The problem was not solved. But I executed in the local environment idea and
> did not throw any exception.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
