You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest versions of the MySQL JDBC driver are able to make use of OpenTelemetry.
Unfortunately the combination of design decisions by OpenTelemetry, MySQL and TestContainers means that if a MySQL TestContainer is started first (in a static, for example) and then the code under test tries to configure OpenTelemetry it will fail because the MySQL driver has already configured OpenTelemetry - it does so when it use by OpenTelemetry for testing whether the database is up.
The MySQL and OpenTelemetry behaviour is reasonable for production deployments, but irritating for tests.
If TestContainers provided a way to set (or modify) the URL used to connect to MySQL this irritation could be avoided (I could tack on the openTelemetry=DISABLED argument).
The text was updated successfully, but these errors were encountered:
Module
MySQL
Proposal
The latest versions of the MySQL JDBC driver are able to make use of OpenTelemetry.
Unfortunately the combination of design decisions by OpenTelemetry, MySQL and TestContainers means that if a MySQL TestContainer is started first (in a static, for example) and then the code under test tries to configure OpenTelemetry it will fail because the MySQL driver has already configured OpenTelemetry - it does so when it use by OpenTelemetry for testing whether the database is up.
The MySQL and OpenTelemetry behaviour is reasonable for production deployments, but irritating for tests.
If TestContainers provided a way to set (or modify) the URL used to connect to MySQL this irritation could be avoided (I could tack on the openTelemetry=DISABLED argument).
The text was updated successfully, but these errors were encountered: