linghengqian commented on issue #30242: URL: https://github.com/apache/shardingsphere/issues/30242#issuecomment-1960875573
> 2:it seems like the Seata Server side don't initiate notifications to other Seata Clients in the transaction group - This is a missing extension point thing as it is difficult to pass in the Seata XID obtained from RPC in the context of a class. Or if you have ideas, you can try to submit PR processing. It seems that you must manually call `RootContext.bind(rpcXid);` in the logical data source using ShardingSphere. Maybe there are some better extension points on Seata that can be used. > 2:i don't know whether or not project A and project B initiate transaction requests to this ShardingSphere Proxy instance through local transactions in Java or Python @linghengqian - Transactions always need to be started manually. On the Java side, you can use JTA annotations like `org.springframework.transaction.annotation.Transactional` or `dataSource.getConnection().setAutoCommit(false)`. On the Python or Golang side, it seems that each ORM framework starts transactions differently. -- 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]
