[Replication] Automatic reload of transformation rules
Open
Nobody has claimed this yet.
good first issue
replication
transformers
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 82
- Avg merge
- 18h 22m
- Merged PRs (30d)
- 51
Description
For replication mode, the schema can change, and the transformation rules might need to change accordingly. Have a way of supporting automatic reloads to avoid having to stop the process each time a new sensitive column is added.
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
No files, tests, or entry points are named. Start by locating how replication mode loads transformation rules and handles schema changes, then determine how rules should reload when a sensitive column is added without stopping the process. Done means the updated rules take effect automatically during replication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100