confluentinc / confluentinc/parallel-consumer
Serialization error handling / flexibility
Open
enhancement
- Dominant language
- Java
- Stars
- 299
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
As discussed in:
- #195
Flexibility around serialisation issues would be useful
ideas:
https://github.com/confluentinc/parallel-consumer/issues/195#issuecomment-1119620569
related:
- #390
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the discussion in #195, especially the linked issue comment, then compare the related context in #390. The issue does not name files, entry points, tests, or a settled behavior, so first clarify which serialization failures should be flexible and define acceptance criteria before locating the implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100