Open lshannon opened 6 years ago
I've done some testing of Spring apps using Spring Cloud Connectors or Spring Boot spring.datasource
configuration to verify similar issues reported on other applications.
The SDCF server is using the org.mariadb.jdbc:mariadb-java-client
JDBC driver for MySQL connections. I've had problems getting that JDBC driver to work with an Azure MySQL service in my testing.
The mysql:mysql-connector-java
JDBC driver seems to work fine with Azure MySQL. If using Hibernate auto DDL creation, you might need to also force the MySQL dialect to org.hibernate.dialect.MySQL55Dialect
instead of the default org.hibernate.dialect.MySQL5Dialect
(that is, 5.5 dialect instead of 5.0).
After further testing, the need to specify the Hibernate dialect depends on the version of Hibernate being used.
Boot 1.5.x has a managed dependency on Hibernate 5.0.x. With this version of Hibernate, the default org.hibernate.dialect.MySQL5Dialect
can be used to successfully initialize the database schema at startup.
Boot 2.0.x has a managed dependency on Hibernate 5.2.x. With this version of Hibernate, the default MySQL5Dialect
will give errors when initializing the schema with several tested MySQL servers. Forcing the dialect to MySQL55Dialect
is required with this version of Hibernate.
Thanks Scott! Will try changing the dialect
Trying to get the SCDF Admin running on PCF (Azure). When the application tries to start up for the first time, I get the error below. Spring Cloud Data Flow Version: 1.30 Azure MySQL: https://azure.microsoft.com/en-us/services/mysql/ Note: This is running on PCF on Azure and the MySQL service is being procured using the Azure Service Broker (https://docs.pivotal.io/partners/azure-sb/index.html)
Seems like something is not correct with the metadata obtained from the service instance, perhaps something to do with Azure and its connection policies around MySQL? Perhaps a DB provisioned in a Cloud Market places by a service broker is not a supported configuration?