-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add example that implements the Metadata SPI for third-party JDBC pools #15507
Comments
Because the Example module looks like it's being refactored, and a number of related issues are being addressed. Therefore, I think this issue should be postponed. (Uncertain about the placement and format of the integration content related to the |
I created a simple test case to help locate this situation. It's at https://github.com/linghengqian/shardingsphere-jdbc-pools-test |
Thx. |
Maybe the content description on the first floor is wrong. After referring to the operation of the website #15563 , I noticed that import |
|
|
I think #19607 would provide a reasonable example for the c3p0 JDBC pool. So I don't think there's more to do with this issue. |
Feature Request
For English only, other languages will not accept.
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Is your feature request related to a problem?
No.
Describe the feature you would like.
In ShardingSphere
5.1.0
, using the JDBC pool is required to have multiple classes that implements its corresponding metadata SPI. This is available at https://shardingsphere.apache.org/document/current/en/dev-manual/data-source/ manifested, but not obvious.Under the
org.apache.shardingsphere.infra.datasource.pool.metadata.type
package, three JDBC pools such asDBCP
,HikariCP
,Tomcat DBCP
(NotTomcat JDBC Pool
) are integrated by default, and implements the correspondingorg.apache.shardingsphere.infra.datasource.pool.metadata.DataSourcePoolMetaData
andorg.apache.shardingsphere.infra.datasource.pool.metadata.DataSourceJdbcUrlMetaData
interfaces. In addition, forHikariCP
, it also implements theorg.apache.shardingsphere.infra.datasource.pool.destroyer.DataSourcePoolDestroyer
interface.In the case of using a third-party
JDBC pool
that does not implement the metadata SPI (usingAlibaba Druid
as an example), the information the user gets is not clear. The user is likely to get something like this.I think an example can be added at https://github.com/apache/shardingsphere/tree/master/examples to provide users with reference. I believe this is also helpful to users of
C3P0
andBeeCP
.The text was updated successfully, but these errors were encountered: