shardingsphere
shardingsphere copied to clipboard
When using the mariadb database in version 5.4.1, the connection prompt is Can not find builder rule: `MariaDB.shardingsphere`
I am using shardingsphere version 5.4.1 and the database is mariadb.
Screenshot of configuration file:
Program specific error information:
2024-05-22 17:41:49.499 WARN 25220 --- [)-172.16.100.71] o.s.b.a.jdbc.DataSourceHealthIndicator : DataSource health check failed
com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Can not find builder rule: MariaDB.shardingsphere
at com.zaxxer.hikari.pool.HikariPool.throwPoolInitializationException(HikariPool.java:596) ~[HikariCP-4.0.3.jar:na]
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:582) ~[HikariCP-4.0.3.jar:na]
at com.zaxxer.hikari.pool.HikariPool.
@zhengfengxu Thank you for your feedback, but I cannot find any relevant configurations about ShardingSphere in your configuration file. Please provide more detailed configurations and usage so that we can solve the problem faster.
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
I met same problem,my yaml configuration is
then give me an error:
when I read the source code,I Found that the SCHEMA_PATH_SYSTEM_SCHEMA_BUILDER_RULE_MAP only support MYSQL_SHARDING_SPHERE、POSTGRESQL_SHARDING_SPHERE、OPEN_GAUSS_SHARDING_SPHERE
Did you provide support for Mariadb?
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Did it close without a response?
I have the same issue. I was considering either changing the DB to MySQL (a lot of work, I wanted to avoid that) or adding a new record to SCHEMA_PATH_SYSTEM_SCHEMA_BUILDER_RULE_MAP using reflection. After a couple of tries, what worked for me was changing the URL to use mysql instead of mariadb: jdbc:mariadb://0.0.0.0:33022/vcemDataSource to jdbc:mysql://0.0.0.0:33022/dataSource. I know this is not ideal, however, it seems to be working fine as of right now. Hopefully, this will be fixed in newer versions. The highest version that I was able to check was 5.4.1 at the time, since there was no higher version of shardingsphere-jdbc-core available in Maven Central.