-
Notifications
You must be signed in to change notification settings - Fork 281
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(ticdc): use admin statement to query async ddl status #11535
Conversation
/retest |
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 @@
## master #11535 +/- ##
================================================
+ Coverage 57.4429% 57.4476% +0.0046%
================================================
Files 851 851
Lines 126421 126463 +42
================================================
+ Hits 72620 72650 +30
- Misses 48394 48404 +10
- Partials 5407 5409 +2 |
d6e66a0
to
9a48d9e
Compare
61432d5
to
2877a38
Compare
2877a38
to
63ccd7c
Compare
c91883d
to
c81d53e
Compare
/retest |
/retest |
[LGTM Timeline notifier]Timeline:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3AceShowHand, asddongmen, hongyunyan 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 |
/retest |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
What problem does this PR solve?
Issue Number: close #11521
What is changed and how it works?
Check List
Tests
Test result in scenarios with a large number of historical DDLs:
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note