spring-projects / spring-projects/spring-pulsar
Consider supporting observations on batch sends
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 205
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
we are only observing single listener (aka record observations) currently. Same approach that spring-kafka has taken. We can look at how to add that to the batch case sensibly once the dust settles on this basic use case.
Originally posted by @onobc in https://github.com/spring-projects-experimental/spring-pulsar/pull/146#discussion_r980645656
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
Review the discussion in pull request #146 and compare the current single-listener observation approach with the batch-send case. Use Spring Kafka's corresponding approach as a reference, then define what consistent batch observations should look like and how completion will be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100