So I replaced the mysql-connector-java file with an older version (8.0.15), but when I go to CF admin settings page and look at CF Server Java Class Path, it still lists the newer version (8.0.25). And I did confirm the location of the file. I have restarted CommandBox and even my laptop, just in case.
I am installing Ignition 8.1.xx on a Red Hat Enterprise Linux 8.5 server. When I attempt to make a database connection to my MySQL database I get an error that connector files are missing. I believe the missing file is mysql-connector-java-8.0.29-1.e18.noarch.rpm. When I proceed to install this file I get the following error:
Sorry for not getting back with feedbacks during this week, but my environment was very unstable and I had to rebuild it on AWS. I have done the driver installation again: tar zxf /usr/mysql-connector-java-5.1.38.tar.gz. Then I realize that i still have the old version mysql-connector-java.jar under /usr/share/java. I then I want to copy the new file from /usr/mysql-connector-java-5.1.38 into the java folder but I realize that this is the file I have there: -rw-r--r--. 1 root root 983914 Dez 2 03:02 mysql-connector-java-5.1.38-bin.jar
I then copy it to /usr/share/java. I change it permissions with chmod 644 and try the sqoop command and get the same errors. Then I change the file name from mysql-connector-java-5.1.38-bin.jar into mysql-connector-java-5.1.38.jar and remove the mysql-connector-java.jar and keep having the same error.
Yes, for Mysql-5.5 and higher your need the latest version of mysql-connector and it cannot be installed using yum, download it from here. After installing it retry sqoop. Also on HDP Sandbox add "--driver com.mysql.jdbc.Driver" to your sqoop command.
Thank you guys. I downloaded and install the connector (tar zxf mysql-connector-java-5.1.38.tar.gz). Then add the --driver and parameters at the sqoop import command. Here is the errors I am getting now:
I updated the connector to mysql-connector-java-8.0.21.jar and it worked again. Now Java has updated to 8u261 and I have the same error again, but there is no new version of the JDBC driver.
d3342ee215