Skip to content
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

Seata+shardingsphere+dynamic >>zpp #26015

Closed
zhangpp2023 opened this issue Jun 2, 2023 · 4 comments
Closed

Seata+shardingsphere+dynamic >>zpp #26015

zhangpp2023 opened this issue Jun 2, 2023 · 4 comments

Comments

@zhangpp2023
Copy link

Bug Report Using Seata+shardingsphere+dynamic >>zpp

For English only, other languages will not accept.

我把shardingsphere数据源交给了dynamic数据源管理,所以我可以通告DS来切换库使用分表规则了,但是我使用了seata1.4.2版本,全局事务无法回滚我,我加了seata代理sharing数据源,可以回滚了,但是回滚的时候,把所有的分区表都查询删除了一遍,我用年月分的,按道理应该查询删除对应的分区表才是啊,请求支持;

Before report a bug, 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.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

Expected behavior

Actual behavior

Reason analyze (If you can)

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

TIM图片20230602163904

TIM图片20230602163904

@zhaojinchao95
Copy link
Contributor

@zhangpp2023 Hi, please translate into english.

@linghengqian
Copy link
Member

我加了seata代理sharing数据源

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 17, 2024
@linghengqian
Copy link
Member

  • Issue closed due to lack of reproducible unit tests.

@linghengqian linghengqian self-assigned this Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants