spring-projects / spring-projects/spring-pulsar
Reading semantics in the reader poller
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 205
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Should we consider using read next w/ timeout? What about when it reaches end of topic? Does the listener just sit and wait for data on the topic to come in?
This is fine for the 1st pass but I think we may want to look into a combination of readNext(int, TimeUnit) + hasMessageAvailable (or something) to avoid the blocking. It does not feel efficient. That being said, this can be a "duly noted" comment and we can noodle on it a bit and handle in later PR. Just capturing my thoughts.
Originally posted by @onobc in https://github.com/spring-projects-experimental/spring-pulsar/pull/342#discussion_r1106593851
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 locating the reader poller and its current blocking read path. Compare the proposed readNext(int, TimeUnit) and hasMessageAvailable approaches, then establish the expected behavior at the end of a topic and when no data is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100