In this example, the database driver is MySQL, and the connection pool is HikariCP, which can be replaced with other database drivers and connection pools. When using ShardingSphere JDBC, the property name of the JDBC pool depends on the definition of the respective JDBC pool and is not defined by ShardingSphere. For related processing, please refer to the class org.apache.shardingsphere.infra.datasource.pool.creator.DataSourcePoolCreator. For example, with Alibaba Druid 1.2.9, using url instead of jdbcUrl in the example below is the expected behavior.

  2.   ds_1:
  3.     dataSourceClassName: com.zaxxer.hikari.HikariDataSource
  4.     jdbcUrl: jdbc:mysql://localhost:3306/ds_1
  6.     password:
  7.   ds_2:
  8.     dataSourceClassName: com.zaxxer.hikari.HikariDataSource
  10.     username: root
  11.     password:
  13.   # Configure other data sources