Thanks for raising this discussion. In short word, users want to use sharding-proxy as a single XAResource and participant in a external XA transaction. We can not support this case currently, please see more details in #12771.
First of all, most of the database we current support such as MySql, PostgresSQL are all XA compatitied. So it could be shame if we lost the XA support in sharding-proxy. We could pass all of the XA related commands (XA START/STOP/COMMIT/ROLLBACK/RECOVER) through to the backend databases in most scenarioes. There could be some issues when the backend databases in a same instance which menas the xid should be unique, and we have to find a way to process it. This could be a big challenge I think. And it is also a good chance to revisit our transaction design. At last I think we should raise a VOTE after this discussion to see if we should support XA scenario. Regades, Zheng Feng lujingshang <lujingsh...@apache.org> 于2021年12月7日周二 下午1:45写道： > Hi all: > Now, we may need to execute the xa start/end... command on the proxy, what > do you think? There are some discussions now: > https://github.com/apache/shardingsphere/issues/12771 > > > Best wishes
