aws-mysql-jdbc should be tollerant to JDBC URL params without value like disableMariaDbDriver about aws-mysql-jdbc HOT 5 CLOSED

Hello @kerny3d

Thank you for raising the issue. We understand this issue is causing inconveniences in your workflows. We'll be investigating this issue and will update you when we have a release. We appreciate your patience.

from aws-mysql-jdbc.

Hello @kerny3d

The fix has been merged, can you please test out our 1.1.2-Snapshot build here and let us know if the issue persists.

Thank you!

from aws-mysql-jdbc.

I confirm the fix.

Thank you.

from aws-mysql-jdbc.

Hi @bobfields

Thanks for reaching out.

It looks like there is an extra ":" in the protocol section of the connection URL that may be causing the issue.

Please let us know if this resolves the issue.

Thank you

from aws-mysql-jdbc.

Yeah I noticed the extra :: and removed the comment. But now we are seeing a certificate path exception, which we did not see with the mariadb driver. Seems to be fixed by the information from https://stackoverflow.com/questions/48286407/ssl-exception-on-java-path-does-not-chain-with-any-of-the-trust-anchors - importing the entire certificate chain (from AWS aurora) into the JVM. Odd that the 2 drivers should work differently for SSL connections.

from aws-mysql-jdbc.