kutouziUk commented on issue #34556: URL: https://github.com/apache/shardingsphere/issues/34556#issuecomment-2633259073
> * I would say no at the moment.我现在会说不。 > * But I guess what you want to do is to change `org.apache.shardingsphere.transaction.base.seata.at.SeataATShardingSphereTransactionManager` to also save the `map` of the real datasource that is not proxied by `org.apache.seata.rm.datasource.DataSourceProxy`. Then use system properties to dynamically switch whether to use the seata client to open transactions? This may require some external testing.但我想你想做的是改变 `org.apache.shardingsphere.transaction.base.seata.at.SeataATShardingSphereTransactionManager` 以保存真实数据源的映射，该`映射`不是由 代理的 `org.apache.seata.rm.datasource.DataSourceProxy` 。然后利用系统属性动态切换是否使用 seata 客户端来开启交易？这可能需要一些外部测试。 What you say makes sense, I tried to implement it before, but I know some of shardingjdbc source code, not completely familiar with it, so it did not succeed. Now I am rewriting SeataATShardingSphereTransactionManager to read seata configuration from the NACOS , rather than seata. conf. I try to implement this from SeataATShardingSphereTransactionManager logic and have a look. Thank you for your answer -- 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: notifications-unsubscr...@shardingsphere.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
