Exclude tidb_binlog & other reserved database names out-of-box
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 291
- Forks
- 131
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
Feature Request
Is your feature request related to a problem? Please describe:
For the database migration that we're performing, we setup DM from Aurora to TiDB first. Then after the migration, we'll revert the replication to replicate from TiDB to Aurora using drainer.
As we switch the replication direction back and forth, we hit an issue where manual changes to tidb_binlog database propagate and break the replication.
Describe the feature you'd like:
In general, any reserved database names for TiDB tools should be excluded from replication pipeline out-of-box.
For instance, in addition to tidb_binlog, I can quickly think of the following:
dm_metasync_diff_inspectortidb_loader
If we get a consensus on this, I think we can apply the same default rule to other replication tools too (e.g. DM).
Describe alternatives you've considered:
- Manually add
tidb_binlogto theignore-schemasconfiguration
Teachability, Documentation, Adoption, Migration Strategy:
N/A
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 tracing the existing ignore-schemas configuration and replication filters for tidb_binlog. Review how the other named tool databases are handled, then add coverage showing that reserved names are excluded by default without manual configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100