-
Notifications
You must be signed in to change notification settings - Fork 41.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to MariaDB 3.1.4 #36394
Comments
This appears to be due to mariadb-corporation/mariadb-connector-j@1d9bee5 which is out of Spring Boot's control. Please report the problem to the maintainers of mariadb-connector-j. In the meantime, you can use |
yes, of course, it can be overrided as you mentioned. But 3.0.10 is included by spring boot 2.7.13 by default and spring claimed responsibility for compatibility of jdk 1.8. So is it possible to choose one available mariadb client version for jdk 1.8? |
I'm afraid not, no. We don't want to get stuck on an old version of the MariaDB JDBC driver so downgrading the dependency for everyone isn't something that we will do. The MariaDB JDBC driver should be compatible with Java 8 (for 3.1.x as well as 3.0.x). Until that incompatibility has been fixed, you should downgrade as needed. |
Hi @wilkinsona , By the way, 3.0.10 is removed from official website https://mariadb.com/kb/en/about-mariadb-connector-j/ |
Thanks for the additional information. Generally speaking, we don't upgrade dependencies to new minor versions in maintenance releases of Spring Boot. However, if 3.0.10 is unusable with Java 8, I wonder if we should make an exception in this case. I'll discuss it with the rest of the team. |
I'm tempted to say we should make an exception since things seem quite broken if we stay on 3.0.10. We'd have to call it out in the release notes so folks can downgrade if they wish. |
We decided to make an exception and upgrade to 3.1.4 in Spring Boot 2.7.x and 3.0.x. Spring Boot 3.1.x has already upgraded. |
Just wanted to let you know that this MariaDB upgrade in Spring Boot 2.7.15 causes a major problem with Hibernate type mappings in native query projections for the MariaDB 10.7 datatype This is the error:
It occurs when upgrading Spring Boot 2.7.14 to 2.7.15 (or higher) with a native query selecting a MariaDB UUID column and mapping it to an interface projection with the field declared as native java UUID type – which hasn't been a problem before. Also, the MariaDB Java Connector 3.0.x series has been updated in the meantime to fix the Java 8 issue: https://mariadb.com/kb/en/mariadb-connector-j-3-0-11-release-notes/ I suppose, downgrading the MariaDB Java Connector in Spring Boot 2.7 isn't an option anymore? For those stumbling upon this issue as well, you have two options:
|
Thanks for the additional info, @tofi86. Unfortunately, we weren't really left with any good options here and tried to pick the least bad of them. As you've noted above, you're free to downgrade to 3.0.x if that's a better fit for your needs. I've updated the changelog for 2.7.15 to this effect as we had missed calling this out as a noteworthy change. |
Alright, thanks for updating the release notes, @wilkinsona! |
current mariadb connector is 3.3.2 while the just released boot 3.2.1 includes mariadb connector 3.2.0: is there a reason for this or I can file a bug asking to update the dependency in the future? |
Spring boot: 2.7.13
mariadb-java-client: 3.0.10
jdk version: 1.8.0_331
database config in yaml:
Please refer to change logs(3.0.9->3.0.10) in mariadb java client---mariadb-corporation/mariadb-connector-j@3.0.9...3.0.10
remainingProperties.remove(keyObj); // it's not allowed in jdk 8 to delete one key in for/foreach function
It works well in jdk 11.
Exception:
The text was updated successfully, but these errors were encountered: