optimize: the class registration method of kryo and fst #2445
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
Codecov Report
@@ Coverage Diff @@
## develop #2445 +/- ##
=============================================
- Coverage 51.75% 51.45% -0.31%
- Complexity 2651 2657 +6
=============================================
Files 521 523 +2
Lines 16919 16938 +19
Branches 2052 2052
=============================================
- Hits 8757 8716 -41
- Misses 7331 7391 +60
Partials 831 831
|
slievrly
reviewed
Mar 25, 2020
serializer/seata-serializer-fst/src/main/java/io.seata.serializer.fst/FstSerializer.java
Outdated
Show resolved
Hide resolved
core/src/main/java/io/seata/core/serializer/SerializerClassRegistry.java
Outdated
Show resolved
Hide resolved
funky-eyes
changed the title
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
optimize the class registration method of kryo and fst
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews