WXingSong commented on issue #37283: URL: https://github.com/apache/shardingsphere/issues/37283#issuecomment-3624368587
> I'm not familiar with Seata. Can you please inquire with the Seata community on my behalf, or could you introduce the purpose of certain Seata configurations you have enabled? I configured everything strictly according to this document： https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/special-api/transaction/seata/ The document states: ``` transaction: defaultType: BASE providerType: Seata ``` ``` seata: enable-auto-data-source-proxy: false ``` I have already tried changing the transaction configuration in Sharding to LOCAL and used Seata’s proxy. ``` transaction: defaultType: LOCAL ``` ``` seata: enable-auto-data-source-proxy: false ``` However, it didn’t work. An error occurred and the transaction was rolled back. Based on our business scenario, global transactions are only needed for cross-service calls, while simple operations within a single service should use local transactions. Does Sharding provide any solution for this? I will also raise this issue in the Seata community. -- 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]
