[
https://issues.apache.org/jira/browse/FLINK-33384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781846#comment-17781846
]
david radley commented on FLINK-33384:
--------------------------------------
It looks like Oracle now recommend using a different driver for mySQL - here
is the discussion
[https://blogs.oracle.com/mysql/post/mysql-connectorj-has-new-maven-coordinates.|https://blogs.oracle.com/mysql/post/mysql-connectorj-has-new-maven-coordinates]
I see that the mySQL tests bring in this dependancy as well.
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>8.0.29</version>
<scope>test</scope>
</dependency>
it is required to resolve an import in test code MySqlMetadata.java.
I could not get these tests to run in main.
> MySQL JDBC driver is deprecated
> -------------------------------
>
> Key: FLINK-33384
> URL: https://issues.apache.org/jira/browse/FLINK-33384
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / JDBC
> Reporter: david radley
> Assignee: david radley
> Priority: Major
>
> I see when running tests on the JDBC connector, I get a warning
> _Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver
> class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered
> via the SPI and manual loading of the driver class is generally unnecessary._
>
> I suggest we change the class to be loaded from the old to the new non
> deprecated class name.
>
> I am happy to implement this and do testing on it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
