How to obtain underlying real data sources in SpringBoot when using ShardingSphere?

[strcpy-s]

I've noticed that all real data sources defined in the YAML configuration are instantiated and wrapped into a ShardingSphereDataSource, which is then stored in ShardingSphereDriver. DriverDataSourceCache. However, this entire process happens outside of Spring Boot's control. As a result, these actual data source instances are not managed by the Spring container, making them inaccessible via standard Spring dependency injection.

So my question is: Is there a recommended way to access these real data sources from within the Spring application context? Or can we make them Spring-managed?

[terrymanu]

No way to get underlying real data sources, ShardingSphere should manage all of them.

[strcpy-s]

@terrymanu Thanks for your help. I'd like to configure Spring Quartz to use an underlying real data source managed by ShardingSphere (e.g., the one behind ds0) as its job store, so that Quartz tables (QRTZ_*) reside in an existing sharded database.

More importantly, I need transactional consistency between Quartz operations and business logic. By sharing the same data source, I can leverage Spring Boot’s declarative transactions without introducing distributed transactions.

Is there a way to expose underlying real data sources from ShardingSphere for this purpose? Any workaround or alternative approach would be greatly appreciated.

[terrymanu]

Just use ShardingSphere as your DataSource, do not need consider about transaction.
ShardingSphere can process distribute transaction as local transaction when you configured transaction rule.

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.