-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metrics(ticdc): Fix kafka compress ratio issue (#11313) #11327
base: release-8.1
Are you sure you want to change the base?
metrics(ticdc): Fix kafka compress ratio issue (#11313) #11327
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## release-8.1 #11327 +/- ##
================================================
Coverage ? 57.3992%
================================================
Files ? 852
Lines ? 125716
Branches ? 0
================================================
Hits ? 72160
Misses ? 48135
Partials ? 5421 |
This is an automated cherry-pick of #11313
What problem does this PR solve?
Issue Number: close #11314
What is changed and how it works?
follow the kafka producer compression ratio definition: https://pkg.go.dev/github.com/IBM/sarama#section-readme
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note