Mysql-connector-java Mysql8
Katja Gains
Hello, we have been running openfire 4.1.5 for a year with MySQL 5.6. Now 5.6 is EOL in a few months so we need to upgrade. Is there a way for me to find out what is the highest version of mysql that openfire 4.1.5 is compatible with?
On Windows you can find mysql-connector-java-xxx.jar file in Openfire\lib folder (should be similar on Linux). Try searching which MySQL versions are supported by that particular xxx version of a connector. Like -j/5.1/en/connector-j-versions.html
The account must have the JDBC JAR file. The default JAR file does not support connectivity to MYSQL8. To connect to MYSQL8, you must upload JAR mysql-connector-java (v8). Learn more about version compatibility in the MySQL article.
To ensure compatibility, we recommend that you use the same versions of MySQL driver and MySQL server for configuring your MySQL account. For example, when using server version 8.0.22, ensure that the driver version is also 8.0.22. If you do not add any JDBC JARs, a default JDBC JAR file is loaded.
If you do not add any JDBC JARs, a default JDBC JAR file is loaded. The default JAR file does not support connectivity to MYSQL8. To connect to MYSQL8, you must upload JAR mysql-connector-java (v5.1.47 or v8).
Upload the JDBC driver and other JAR files that you want to use into SLDB. Click to add a new row. Add each JDBC JAR file in a separate row. For more information about JDBC drivers and downloading the appropriate driver for your account, see Downloading the JDBC Driver.
The file can be in SLDB, on the host machine that is hosting the JCC, or at any other remote location. For a local file, click to select the appropriate file using the file browser. You can also upload the file using any protocol such as https, ftp, sldb, and sftp.
Using a large batch size could use up the JDBC placeholder limit of 2100. If the batch size is too large, sending a single batch request to the database server can take too long and it would time out. You should test and monitor the performance with different batch sizes and decide the best batch size.
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:
The parameter "&serverTimezone=UTC" is added to prevent the database garbled problem caused by the time zone, where UTC is the universal time, which is the zero time zone. If the time used by the user's system, report server, etc. is Beijing time zone, that is, the East Eighth District, the data time that will appear in the FineReport data preview interface is eight hours faster than the time in the database, and the parameter can be modified as &serverTimezone=GMT%2B8 , where "GMT%2B8" is the East Eighth District of Beijing time. It can be ensured that the time field in the database is consistent with the time field in the Finereport data preview interface.
1) The administrator logs in to the decision-making platform, clicks Manage > Data Connection > Data Connection Management, clicks New Data Connection, and selects MySQL8 under all options, as shown in the following figure:
Note: If a non-admin user wants to configure a data connection, the administrator needs to assign him the authority to manage the data connection node under the system. For details, please refer to Data Connection Authorization.
2) Enter the corresponding data connection information according to the configuration information in Section II.2 of this article. The advanced settings are optional. For details, please refer to: [Platform] Configure data connection . After entering the information, the interface is as shown below:
Due to the numerous minor versions of MySQL 8, the connection cannot be guaranteed after replacing the driver package. Therefore, qualified users are recommended to use the MySQL 8.0.20 version database directly.
2) Download the connection driver package corresponding to the current MySQL minor version from the MySQL official website. Take MySQL 8.0.17 as an example, download the driver package mysql-connector-java-8.0.17.jar
In the third scenario, we set up a connection where we connect to Oracle 18 and MySQL 8 using external drivers from AWS Glue ETL, extract the data, transform it, and load the transformed data to Oracle 18.
This post is tested for mysql-connector-java-8.0.19.jar and ojdbc7.jar drivers, but based on your database types, you can download and use appropriate version of JDBC drivers supported by the database.
We provide this CloudFormation template for you to use. Review and customize it to suit your needs. Some of the resources deployed by this stack incur costs as long as they remain in use, like Amazon RDS for Oracle and Amazon RDS for MySQL.
This step automatically launches AWS CloudFormation in your AWS account with a template. It prompts you to sign in as needed. You can view the CloudFormation template from within the console as required.
Before creating an AWS Glue ETL, run the SQL script (database_scripts.sql) on both the databases (Oracle and MySQL) to create tables and insert data. For more information about connecting to the RDS DB instance, see How can I troubleshoot connectivity to an Amazon RDS DB instance that uses a public or private subnet of a VPC?
You can find the database endpoints (url) on the CloudFormation stack Outputs tab; the other parameters are mentioned earlier in this post. If you use another driver, make sure to change customJdbcDriverClassName to the corresponding class in the driver.
In this post, we showed you how to build AWS Glue ETL Spark jobs and set up connections with custom drivers with Oracle18 and MySQL8 databases using AWS CloudFormation. You can use this solution to use your custom drivers for databases not supported natively by AWS Glue.
Once this is done, you'll want to download a copy of the attached driver and place it in the same folder as your installer jar. This process will only work with the jar installer. The following command will run the installer with the driver you have downloaded:
java -cp mysql-connector-java-5.1.46.jar;yellowfin-7.4.6-20180508-full.jar com.hof.installer.InstallerMove through your installation as normal. Once completed, attempt to start Yellowfin. Give it some time to unpack the webapps folder and then stop Yellowfin.
My Ansible/Rundeck host is an Ubuntu 20.04 LTS system. I installed Ansible to tinker and then installed Rundeck. Once I was able to get the two talking and working properly (in my mind), I thought it would be best to move Rundeck to a production level DB engine instead of H2. I installed MySQL on the same host and setup the DB and the DB user as directed in the Rundeck docs. I then modified the RD properties file as the same document instructs but I keep getting a failure to connect to the database.
I then downloaded the Oracle MySQL jdbc driver and placed it in the var/lib/rundeck/lib folder and changed the driver class name in the properties file and then I received my but that could not connect. I was able to detect in the system.log output: ' Unable to load class: com.mysql.jc.jdbc.Driver from ClassLoader:org.springframework.boot.loader.'. Obviously the MySQL jdbc driver is not being loaded or possibly found at all. I placed the file in /var/lib/rundeck/lib. Do I need to give the file any special permissions or should it be named something specific. I used wget to download it while in Ubuntu. The file name is mysql-connector-java-8.0.22.jar and it transferred without any issue.
d3342ee215