Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does Shardingsphere version 5.4.0 support seata transaction tcc mode? #29686

Closed
Python-IBM opened this issue Jan 9, 2024 · 3 comments
Closed

Comments

@Python-IBM
Copy link

Python-IBM commented Jan 9, 2024

Question

For English only, other languages will not accept.

Before asking a question, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Does Shardingsphere version 5.4.0 support seata transaction tcc mode?

Copy link

github-actions bot commented Feb 8, 2024

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

@github-actions github-actions bot added the stale label Feb 8, 2024
@linghengqian
Copy link
Member

  • I completed clarification in Bump io.seata:seata-all for testing to 2.0.0 #30146 that when using org.apache.shardingsphere:shardingsphere-transaction-base-seata-at you should not actually use any Seata Java API. This includes but is not limited to the use of TCC related classes as follows,
    • io.seata.rm.tcc.api.TwoPhaseBusinessAction
    • io.seata.rm.tcc.api.BusinessActionContextParameter
    • io.seata.rm.tcc.api.LocalTCC
  • Using TCC-related Java classes is actually behavior that is not defined by unit tests, which may require a new module. I assume you have related ideas for adding unit tests?
  • This will most likely require some changes on Seata's side, see TCC模式怎么通过纯api方式使用呢? incubator-seata#4828.

Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

@github-actions github-actions bot added the stale label Mar 18, 2024
@apache apache locked and limited conversation to collaborators Jul 7, 2024
@terrymanu terrymanu converted this issue into discussion #32023 Jul 7, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

3 participants