incubator-seata
incubator-seata copied to clipboard
:fire: Seata is an easy-to-use, high-performance, open source distributed transaction solution.
- [ ] I have registered the PR [changes](https://github.com/seata/seata/tree/develop/changes). ### Ⅰ. Describe what this PR did seata 服务端 适配 gts消息 ### Ⅱ. Does this pull request fix one issue? 开源之夏2022...
- [ ] I have registered the PR [changes](https://github.com/seata/seata/tree/develop/changes). ### Ⅰ. Describe what this PR did support mysql update join sql ### Ⅱ. Does this pull request fix one issue?...
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description saga模式定义ServiceTask的Output表达式错误的话,会出现空指针异常 ### Ⅱ. Describe what happened output...
- [ ] I have registered the PR [changes](https://github.com/seata/seata/tree/develop/changes). ### Ⅰ. Describe what this PR did - Add Tencent Polaris Registry (Configuration & Service Discovery) support for Seata framework. ###...
- [ ] I have registered the PR [changes](https://github.com/seata/seata/tree/develop/changes). ### Ⅰ. Describe what this PR did doAcquireLocks实现里把SQLException都吞掉了,估计是因为认为出现这种异常都是因为唯一键冲突,所以默认为这个是锁冲突。当其他异常发生时,他也把异常吞掉就不合适了。 这个pr只在catch到SQLIntegrityConstraintViolationException时返回false,其余情况直接throw。 另外可以讨论下这种异常是不是在这层吃掉,哪怕他只是个唯一键冲突异常。 ### Ⅱ. Does this pull request fix one issue? fixes https://github.com/seata/seata/issues/4941...
- [ ] I have registered the PR [changes](https://github.com/seata/seata/tree/develop/changes). ### Ⅰ. Describe what this PR did 新增配置client.undo.dataValidation.skip ,表示可跳过校验的列表(以,分隔) 此配置在client.undo.dataValidation = true时生效。 满足跳过的逻辑是:**_beforeImage, afterImage , currentImage 其中某个的tableName存在于这个skip列表中_**。 新增了test,以及修复了之前test不严谨的部分(由于tableMeta被mock了所以setTableMeta会覆盖掉tableName) ### Ⅱ. Does...
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description JVM startup parameters are not uniform and...
### Ⅰ. Issue Description TC端发生异常后,异常sqlexception没有包装回传给client端 ### Ⅱ. Describe what happened TC端在写入【lock_table】表时,因为‘row_key’字段数据超长,造成【lock_table】表数据写入失败,但是该异常没有回传给client端。在client端的日志中,只提示  ### Ⅲ. Describe what you expected to happen TC端应该将异常  包装后返回给client端,client打印出或者进行处理 ### Ⅵ. Environment: - JDK version :...
Signed-off-by: slievrly - [x] I have registered the PR [changes](https://github.com/seata/seata/tree/develop/changes). ### Ⅰ. Describe what this PR did optimize read of storage configuration 1. `ParameterParser` only responsible for startup parameters 2....
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description 启动时如果数据库加载过久会hang住,此时在jstack看到的现象是有等待,但没有死锁,但实际上这个跟死锁效果一样。 这个文章有提到 https://stackoverflow.com/questions/28631656/runnable-thread-state-but-in-object-wait 之前的死锁问题在https://github.com/seata/seata/pull/4107 有解决,但现在看来这个方案因为涉及静态加载也会变成另一种死锁 ### Ⅱ....