redpanda-data / redpanda-data/schema-migration
ordering of export to cater for Subjects that reference other subjects
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 5
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 1
Description
Need to look at the ordering of the export.. (possibly sort them based on schema ID.)
to handle scenario where subjects have "references" to other subjects.
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
Start by locating the export implementation and examining how subjects and their schema IDs are collected. Trace the handling of subject references and determine the required dependency order; done means exported subjects are ordered so referenced subjects are available before the subjects that depend on them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100