linghengqian commented on issue #32734: URL: https://github.com/apache/shardingsphere/issues/32734#issuecomment-2322732123
- You actually didn't understand what I meant. You are completely calling the public API of Java JDBC, and you don't really touch upon the essence of metadata changes in ShardingSphere JDBC DataSource. - If you want to implement the ambiguous concept of `dynamic tenant splicing`, you must change the processing of metadata by ShardingSphere, which is the so-called downstream ShardingSphere private fork, because it conflicts with the design of ShardingSphere. You can propose a draft PR to explain why this feature will not conflict with the design of ShardingSphere, but `dynamic tenant splicing` are actually not covered by the current design of ShardingSphere. - To obtain `ContextManager` from ShardingSphere JDBC DataSource, please refer to the unit test of https://github.com/apache/shardingsphere/pull/31825 . ShardingSphere Agent operates ShardingSphere metadata with a completely independent design. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
