linghengqian commented on issue #33791: URL: https://github.com/apache/shardingsphere/issues/33791#issuecomment-2509571398
@26903651 - What I can tell you clearly is that a lot of unit tests for shardingsphere's seata integration are not actually in shardingsphere's master branch because https://github.com/apache/incubator-seata/issues/6614 is not resolved. 1. Shardingsphere jdbc's seata integration and seata client 2.2.0 can be used under both HotSpot VM and GraalVM Native Image. 2. Shardingsphere proxy's seata integration and seata client 2.2.0 can be used under HotSpot VM, but have not been tested under shardingsphere proxy native under GraalVM Native Image. The reason why the relevant unit tests are not in shardingsphere's master branch is that https://github.com/apache/incubator-seata/issues/7039 is not resolved. - In order to support GraalVM Native Image, all ShardingSphere support for Seata Client 1.x has been abandoned. See https://github.com/apache/shardingsphere/issues/29052 , https://shardingsphere.apache.org/document/current/cn/user-manual/shardingsphere-jdbc/special-api/transaction/seata/ and [跨越 MySQL 边界 -- GraalVM Native Image 下 ShardingSphere JDBC 的 Seata AT 集成 https://www.yuque.com/linghengqian/meve2v/es8d3a8a18odao7x](https://www.yuque.com/linghengqian/meve2v/es8d3a8a18odao7x) . - Back to the current issue, there is actually not much to do except updating the documentation. - Of course, in order to further resolve the dependency conflicts of Seata Client, I tend to change the seata client used by shardingsphere for testing from 2.1.0 to 2.2.0 . We all know that the Docker Image of Seata 2.2.0 currently has 593 CVEs, which means we need to speed up. See https://github.com/oracle/graalvm-reachability-metadata/issues/542#issuecomment-2446645418 . -- 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]
