Releases
v0.5.2
[#988 ] support Consul configuration center
[#1043 ] support sofa-rpc
[#987 ] optimize the use of reentrantLock instead of spinlock in concurrent scenarios within the same transaction
[#943 ] fix configuration wait timeout when there is no corresponding file configuration item
[#965 ] fix PreparedStatement where in,between problem
[#929 ] optimize GlobalSession for the first time to wait for locks
[#967 ] optimize partial log description
[#970 ] fix unable to read flush-disk-mode configuration item problem
[#916 ] optimize the readable index problem of decoding
[#979 ] optimize copyright
[#981 ] optimize pom dependencies, use caffine instead of guava cache, junit upgrade to junit5, use junit5 to transform original testng unit tests
[#991 ] optimize the header of the core module import
[#996 ] fix maven-surefire-plugin compilation error in mac environment
[#994 ] Fix ByteBuffer multiple flip problem
[#999 ] change the community's email subscription address
[#861 ] optimize the FailureHandler to periodically get the retrieved transaction result and print the successful result
[#802 ] optimize the lambda code style in GlobalTransactionalInterceptor
[#1026 ] fix troubleshooting for data* code files, add local transaction file exclusion path
[#1024 ] fix Consul module SPI configuration file path problem
[#1023 ] add the seata-all.jar for client full dependency
[#1029 ] fix the delay rollback caused by no channel when the client is restarting
[#1027 ] fix release-seata can not generate zip file problem
[#1033 ] fix createDependencyReducedPom to generate redundant xml problem
[#1035 ] fix branchCommit/branchRollback in TCC mode, but branchId is null
[#1040 ] refactor exceptionHandleTemplate and fix the problem that cannot be returned when the GlobalRollback branch throw exception
[#1036 ] replace Chinese comment with English comment
[#1051 ] optimize to check data changes when rollback, stop rollback if there is no data change
[#1017 ] optimize the processing logic of mysql undo executor construct undo sql
[#1063 ] fix the problem that the new transaction id conflict fails after the server is restarted after the server is restarted.
You can’t perform that action at this time.