feature: add fastjson2 serializer support #6904
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
funky-eyes
added
type: feature
funky-eyes
reviewed
Oct 9, 2024
| /** | ||
| * The fastjson2. | ||
| * <p> | ||
| * Math.pow(2, 5) |
There was a problem hiding this comment.
Suggested change
| * Math.pow(2, 5) | |
| * Math.pow(2, 6) |
| import org.apache.seata.core.serializer.SerializerSecurityRegistry; | ||
|
|
||
| /** | ||
| * @Author GoodBoyCoder |
| import org.apache.seata.core.serializer.Serializer; | ||
|
|
||
| /** | ||
| * @Author GoodBoyCoder |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ⅰ. Describe what this PR did
支持 fastJson2序列化RPC消息
Support fastJson2 serialization of RPC messages
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Configure the serialization method to fastjson2
Ⅴ. Special notes for reviews
关于是否统一序列化类型为FastJson（即去除fastjson1，统一采用fastjson2），这个很大程度依赖与fastjson2的兼容性，undolog的对象结构复杂，大概率做不到100%兼容，故这里应该需要区分fastjson1和fastjson2，而如果RPC统一为fastjson，两边的配置叫法就不是很统一
Whether to unify the serialization type to FastJson (i.e., remove fastjson1 and unify to fastjson2) depends largely on the compatibility with fastjson2. The object structure of undolog is complex and it is highly unlikely to be 100% compatible. Therefore, it is necessary to distinguish between fastjson1 and fastjson2. If RPC is unified as fastjson, the configuration names on both sides will not be very unified.