-
Notifications
You must be signed in to change notification settings - Fork 287
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
sink: fix kafka max message size inaccurate issue. #3002
sink: fix kafka max message size inaccurate issue. #3002
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest LGTM
Co-authored-by: Neil Shen <overvenus@gmail.com>
…Hand/ticdc into fix-sink-kafka-max-message-size
/run-all-tests |
/run-integration-tests |
Codecov Report
@@ Coverage Diff @@
## master #3002 +/- ##
================================================
- Coverage 57.2251% 57.0601% -0.1650%
================================================
Files 163 188 +25
Lines 19453 20736 +1283
================================================
+ Hits 11132 11832 +700
- Misses 7261 7735 +474
- Partials 1060 1169 +109 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: c27a5eb
|
/run-kafka-tests |
1 similar comment
/run-kafka-tests |
In response to a cherrypick label: new pull request created: #3046. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created: #3047. |
In response to a cherrypick label: new pull request created: #3048. |
In response to a cherrypick label: new pull request created: #3049. |
What problem does this PR solve?
try to close #2962
What is changed and how it works?
maximumRecordOverhead
, which was introduced by the sarama client.max-message-size
at the producer level, default to512m
.max-message-size
only works for the encoder.Debug
whenAppendRowChangedEvent
in json encoder.Check List
Tests
Code changes
Side effects
Related changes
Release note