-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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 mariadb-java-client from 2.7.5 to 3.0.4 #24570
Conversation
Btw, no changes compared to #23249 except for the version property. |
@famod but does that mean you end up with WARN messages in your logs for normal operations? |
@gsmet not in general, but I saw two warnings on a clean DB when liquibase runs for the first time. It was warning that DATABASECHANGELOG doesn't exist (and the lock table). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, thanks!
I see you asked for a backport. Is there anything pressing in the upgrade? |
Well, not really. Fits a .0 rather well? I'm not sure there will be any changes to the 2.x driver. |
Yeah we are back to regular cycles. I'm on the verge for this one, I'll decide when doing the backport round :). |
Thanks for backporting, @gsmet! |
https://mariadb.com/docs/release-notes/mariadb-connector-j-3-0/3-0-4/
Another try, after #23249 and #23530. The issues that popped up back then have been addressed, AFAICS.
A quick test run in my project didn't reveal any issues (just more WARN-chattiness by
org.mariadb.jdbc.message.server.ErrorPacket
).