Drainer: SyncDDL switcher does not work when syncing to oracle
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
-
What did you do?
If possible, provide a recipe for reproducing the error.
set SyncDDL= false in configuration file.
on TiDB client, you operation non "truncate table **" statement, the drainer will stop.
See: https://github.com/pingcap/tidb-binlog/pull/1130 -
What did you expect to see?
the drainer will not stop -
What did you see instead?
the drainer will stop -
Please provide the relate downstream type and version of drainer.
(rundrainer -Vin terminal to get drainer's version)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced PR 1130 and the drainer path handling SyncDDL=false when syncing to Oracle. Reproduce the report with SyncDDL disabled and a non-TRUNCATE operation from a TiDB client; done means the drainer continues running instead of stopping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100