feature: support zstd compressor #3951
Merged
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
reviewed
Aug 15, 2021
bom/pom.xml
Outdated
| @@ -372,6 +372,31 @@ | |||
| <artifactId>seata-sqlparser-druid</artifactId> | |||
| <version>${project.version}</version> | |||
| </dependency> | |||
| <dependency> | |||
| <groupId>com.github.luben</groupId> | |||
| <artifactId>zstd-jni</artifactId> | |||
Codecov Report
@@ Coverage Diff @@
## develop #3951 +/- ##
=============================================
- Coverage 40.30% 40.26% -0.05%
- Complexity 3070 3077 +7
=============================================
Files 687 689 +2
Lines 23231 23218 -13
Branches 2868 2818 -50
=============================================
- Hits 9364 9348 -16
+ Misses 12997 12975 -22
- Partials 870 895 +25
|
slievrly
reviewed
Aug 24, 2021
slievrly
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
Ⅱ. 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