-
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
codec(ticdc): canal-json support large message handle #9384
Merged
ti-chi-bot
merged 50 commits into
pingcap:master
from
3AceShowHand:canal-json-support-large-message-handle
Jul 19, 2023
Merged
codec(ticdc): canal-json support large message handle #9384
ti-chi-bot
merged 50 commits into
pingcap:master
from
3AceShowHand:canal-json-support-large-message-handle
Jul 19, 2023
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
ti-chi-bot
bot
added
release-note-none
Denotes a PR that doesn't merit a release note.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
labels
Jul 12, 2023
3AceShowHand
changed the title
[DNM]codec(ticdc): canal-json support large message handle
codec(ticdc): canal-json support large message handle
Jul 12, 2023
ti-chi-bot
bot
added
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
and removed
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
labels
Jul 19, 2023
3AceShowHand
force-pushed
the
canal-json-support-large-message-handle
branch
from
July 19, 2023 05:59
6d9f964
to
4600e41
Compare
ti-chi-bot
bot
added
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
and removed
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
labels
Jul 19, 2023
3AceShowHand
requested review from
sdojjy,
asddongmen,
CharlesCheung96 and
nongfushanquan
July 19, 2023 06:05
sdojjy
approved these changes
Jul 19, 2023
ti-chi-bot
bot
added
needs-1-more-lgtm
Indicates a PR needs 1 more LGTM.
approved
labels
Jul 19, 2023
asddongmen
approved these changes
Jul 19, 2023
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: asddongmen, sdojjy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
Indicates a PR needs 1 more LGTM.
labels
Jul 19, 2023
[LGTM Timeline notifier]Timeline:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
lgtm
release-note-none
Denotes a PR that doesn't merit a release note.
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
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.
What problem does this PR solve?
Issue Number: close #9382, close #9383
What is changed and how it works?
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