linghengqian commented on issue #34914:
URL:
https://github.com/apache/shardingsphere/issues/34914#issuecomment-2706581349
> I noticed that there are no examples for BASE transactions, even though
they are described in the documentation.
- I guess you are referring to Seata's AT mode. ShardingSphere currently
only focuses on Seata's AT mode. ShardingSphere has not done unit testing for
Seata's TCC mode. ShardingSphere has never supported Seata's SAGA mode and XA
mode.
- The CI of https://github.com/apache/shardingsphere/tree/master/examples is
actually broken, see
https://github.com/apache/shardingsphere/actions/runs/13703021727 . Since this
module is written in FreeMarker, it's hard to say that I personally know how to
fix CI.
> and I couldn’t find any up-to-date examples or documentation for
configuring BASE transactions.
# For document
- The seata documentation for `shardingsphere jdbc` is at
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/special-api/transaction/seata/
, and the seata documentation for `shardingsphere proxy` is at
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/optional-plugins/seata-at/
.
# For unit test about postgresql
- There are indeed no normal integration tests for seata currently.
- However, shardingsphere did write integration tests for `postgresql` and
`seata server` against the `graalvm native image` environment.
- The integration tests for Seata integration of `ShardingSphere JDBC` are
located at
https://github.com/apache/shardingsphere/blob/master/test/native/src/test/java/org/apache/shardingsphere/test/natived/jdbc/transactions/base/SeataTest.java
.
- The integration tests for the Seata integration of `ShardingSphere Proxy`
are at
https://github.com/apache/shardingsphere/blob/master/test/native/src/test/java/org/apache/shardingsphere/test/natived/proxy/transactions/base/SeataTest.java
. Note that this unit test is broken due to #34816 . I can hardly say that I
know how to fix #34816 .
- Note that both of these unit tests target only a single microservice. Due
to https://github.com/apache/incubator-seata/issues/6614 , I intentionally did
not test the transaction propagation feature across microservices in the master
branch of shardingsphere.
# For example git about mysql
- We introduce a premise that the shardingsphere document is built with
`hugo`. `hugo` supports `mermaid` drawing. But for me, testing the
shardingsphere document's support for `mermaid` is a very troublesome thing.
This results in the seata document currently having no pictures.
- To explain the history of Seata integration of ShardingSphere, I wrote a
Chinese article https://www.yuque.com/linghengqian/meve2v/es8d3a8a18odao7x ,
which demonstrated how to enable transaction propagation across microservices
of `Seata 2.2.0` for `ShardingSphere jdbc 5.5.1` and `MySQL 9.1.0` in multiple
`Spring Boot 3.3.5` microservices. This article does use the `Yuque` editor
specifically to draw pictures.
- I personally don't have the energy to translate this article. But the
corresponding git of this article is located at
https://github.com/linghengqian/shardingsphere-seata-playground , I believe it
is enough to explain a lot of things. Reading this article does require an
advance understanding of spring boot, seata, shardingsphere, and mysql.
-
> P.S. I'm aware that BASE transactions require a SEATA server, but I wanted
to make sure that such transactions are supported first to move forward.
- Okay, the premise we're going to introduce is that we're only going to
talk about the AT mode of Seata.
- This obviously requires SQL dialect parsing to be implemented on the Seata
side, and Seata implements dialect parsing through Alibaba Druid by default.
- seata also has an optional antlr4 dialect parsing module, but for more
complicated reasons that module is practically unusable.
- Therefore, the seata integration of ShardingSphere actually only supports
the databases mentioned in
https://github.com/apache/incubator-seata/tree/v2.2.0/script/client/at/db .
Currently they are `dm`, `mysql`, `oracle`, `postgresql`, and `sqlserver`.
-
https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/special-api/transaction/seata/
gives some examples of related Docker Images.
> When using ShardingSphere’s Seata integration module, the database
instance connected to ShardingSphere should implement both ShardingSphere’s
dialect parsing support and Seata AT mode’s dialect parsing support. This type
of database includes but is not limited to `mysql`, `gvenzl/oracle-free`,
`gvenzl/oracle-xe`, `postgres`, `mcr.microsoft.com/mssql/server` and other
Docker Images.
- Databases with this feature include but are not limited to the following
Docker Images,
1. Third-party Docker Image `mysql` for MySQL Community Server
2. Third-party Docker Image `gvenzl/oracle-free` for Oracle Database Free
3. Third-party Docker Image `gvenzl/oracle-xe` for Oracle Database Express
Edition (XE)
4. Third-party Docker Image `postgres` for PostgreSQL
5. Official Docker Image `mcr.microsoft.com/mssql/server` for Microsoft SQL
Server
- Seata also supports `DM` represented by `DM8`, but that is a commercial
database. `Dameng` does not provide docker image to non-paying users. Refer to
https://www.dameng.com/DM8.html . Seata obviously supports `DM8` in a mock way,
and Shardingsphere will not try to test this database that lacks docker image
in the master branch.
--
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
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
