kutouziUk opened a new issue, #34556: URL: https://github.com/apache/shardingsphere/issues/34556
**version** Seata: 2.0.0 ShardingJDBC: 5.3.2 **question** After Seata is integrated into distributed transactions, adding @Transactional(rollbackFor = Except.class) on the business methods AT this point will execute the Seata AT process to execute the transaction. However, there are many scenarios where a single data source is being manipulated and TransactionType. LOCAL is sufficient. Is there a solution that only executes the Seata AT Spring transactions process in the case of multiple data sources, and that @Transactional(rollbackFor = Exception.class) executes normal Spring transactions in the case of a single data source? -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
