redpanda-data / redpanda-data/connect
Detect branch misalignment issues
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
Currently if the processors that you execute within a branch change the number of resulting messages then the result map fails. However, if the ordering of messages changes (due to group_by, etc), then we can potentially also catch this issue by adding context to the messages similar to the switch processor: https://github.com/Jeffail/benthos/blob/master/lib/processor/switch.go
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 reading the branch processor documentation and the message-context handling in lib/processor/switch.go. Trace how branch result maps are matched when processors use group_by or otherwise reorder messages; done means branch misalignment is detected and reported rather than producing an incorrect result map.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100