redpanda-data / redpanda-data/schema-migration
Support for `MODE`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 5
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 1
Description
Mode records look like this, so quite similar to CONFIG.
{
"topic": "_schemas",
"key": "{\"keytype\":\"MODE\",\"subject\":\"foo\",\"magic\":0,\"seq\":7,\"node\":0}",
"value": "{\"mode\":\"READONLY\"}",
"timestamp": 1718098531270,
"partition": 0,
"offset": 7
}
During import, they should probably be applied last (with the seq and node from the key dropped), so that a topic isn't made READWRITE whilst it's still being imported.
Contributor guide
No contributing guide indexed for this repository
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 or tests are named; start by locating the import handling for CONFIG records and the code that parses schema migration records. Trace how record ordering and key fields are handled, then verify that MODE records are applied last, with seq and node omitted while the mode value is retained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100