apache / apache/incubator-seata
If you use the Ata mode of seata and the read and write separation of ShardingSphere, you don't need to rely on ransaction-base-seata-at
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
我看 ransaction-base-seata-at 这个包里面数据分片时候会创建 SeataATShardingTransactionManager 读写分离的时候没有创建
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ransaction-base-seata-at package and the SeataATShardingTransactionManager creation path. Compare behavior for data sharding with behavior for ShardingSphere read/write separation, then verify whether the dependency and transaction-manager setup are consistent in both cases. Done means the expected AT transaction behavior is clearly established for read/write separation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100