kafka(ticdc): ddl sink close the underline sink if send ddl or checkpoint failed and refactor the kafka ddl sink (#12112)#12677
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
@3AceShowHand This PR has conflicts, I have hold it. |
|
@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide. DetailsInstructions 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 ti-community-infra/tichi repository. |
There was a problem hiding this comment.
Code Review
This pull request refactors the DDL sink to close the underlying sink upon failure and wraps Kafka send errors at the producer level. However, there are critical issues that must be addressed: unresolved git conflict markers are present in multiple files, including mq_ddl_sink.go and pulsar_ddl_sink.go. Additionally, a redundant import alias cerror was introduced in pkg/sink/kafka/v2/factory.go which should be replaced with the existing errors import.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Codecov Report❌ 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.5 #12677 +/- ##
================================================
Coverage ? 54.0094%
================================================
Files ? 1027
Lines ? 139496
Branches ? 0
================================================
Hits ? 75341
Misses ? 58563
Partials ? 5592 🚀 New features to boost your workflow:
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3AceShowHand The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold |
|
/retest |
|
/hold |
|
/hold |
|
/retest |
|
/unhold |
This is an automated cherry-pick of #12112
What problem does this PR solve?
Issue Number: close #12666, close #12096
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