redpanda-data / redpanda-data/redpanda
Schema validation on broker
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Who is this for and what problem do they have today?
According to [1], Redpanda is currently not validating messages if a schema is defined during writes on the broker.
So, if I define a schema for a specific topic/subject, I can still produce and insert invalid/incompatible data, right?
So, right now I can only trust that producers are sending messages with the correct schema. This is potentially dangerous, since invalid data could be considered a poison pill, as consumers are unable to handle the messages.
JIRA Link: CORE-805
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 reviewing the CORE-805 JIRA link and the referenced Slack discussion for the existing decision and requirements. Define done as broker-side validation preventing invalid or incompatible writes when a schema is defined for a topic or subject, with the relevant behavior and compatibility cases agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100