marcosschroh / marcosschroh/python-schema-registry-client
Please suport Schema References
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 178
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Description
Confluent Platform 5.5.0 support [Schema References](https://docs.confluent.io/current/schema-registry/serdes-develop/index.html#schema-references), the ability of a schema to refer to other schemas.
[Here's](https://www.confluent.io/blog/multiple-event-types-in-the-same-kafka-topic/) a blog post that goes a bit into detail.
The schema you want to register contains a reference:
```json
{
"namespace": "my.little.schema",
"name": "Test",
"type": "record",
"fields": [
{
"name": "name",
"type": {
"name": "Name",
"type": "some.other.schema" <====
}
}
]
}
```
The json you sent to the SR contains a `references` section, listing all referenced schemas with versions:
```json
{
"schema": "...",
"references": [
{
"name": "some.other.schema",
"subject": "name",
"version": 42
}
]
}
```
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 schema registration request path and its existing request serialization, then compare it with the linked Confluent Schema References documentation. Done means registration requests can represent and send the listed references, including their names, subjects, and versions, with tests covering the new request shape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100