This is an automated email from the ASF dual-hosted git repository. yy2so pushed a commit to branch yy2so-patch-1 in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
commit 218642e7d2dcb47df77406a4973a476d27a3aed9 Author: Yacine Si Tayeb <[email protected]> AuthorDate: Tue Jan 3 17:13:20 2023 +0800 Update limitations.en.md Updating the doc. --- .../content/features/transaction/limitations.en.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/document/content/features/transaction/limitations.en.md b/docs/document/content/features/transaction/limitations.en.md index 158ed3017a5..7d45b2f90ea 100644 --- a/docs/document/content/features/transaction/limitations.en.md +++ b/docs/document/content/features/transaction/limitations.en.md @@ -3,26 +3,26 @@ title = "Limitations" weight = 2 +++ -Though Apache ShardingSphere intends to be compatible with all distributed scenario and best performance, under CAP theorem guidance, there is no sliver bullet with distributed transaction solution. +Although Apache ShardingSphere aims at being compatible with all distributed scenario and providing the best performance, under the CAP theorem guidance, there is no sliver bullet with distributed transaction solution. -Apache ShardingSphere wants to give the user choice of distributed transaction type and use the most suitable solution in different scenarios. +The Apache ShardingSphere community chose instead to give the users the ability to choose their preferred distributed transaction type and use the most suitable solution according to their scenarios. ## LOCAL Transaction ### Unsupported -* Do not support the cross-database transactions caused by network or hardware crash. For example, when update two databases in transaction, if one database crashes before commit, then only the data of the other database can commit. +* Does not support the cross-database transactions caused by network or hardware crash. For example, when updating two databases in transaction, if one database crashes before commit, then only the data of the other database can commit. ## XA Transaction ### Unsupported -* Recover committing and rolling back in other machines after the service is down; -* MySQL, in the transaction block, the SQL execution is abnormal, and run `Commit`, and data remains consistent; -* After XA transactions are configured, the maximum length of the storage unit name can not exceed 45 characters. +* Recover committing and rolling back in other machines after the service is down. +* MySQL, in the transaction block, the SQL execution is abnormal, and run `Commit`, and data remains consistent. +* After XA transactions are configured, the maximum length of the storage unit name cannot exceed 45 characters. ## BASE Transaction ### Unsupported -* Do not support isolation level. +* Does not support isolation level.
