[Enhancement] Implement retry consuming based on Pulsar message middleware
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
This issue aims to implement retry consuming based on Pulsar middleware
### Describe the solution you'd like
Implement a retry consuming based on Pulsar
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) *
Contributor guide
Research direction
Start by reviewing the EventMesh Pulsar middleware area and existing message-consumption behavior; the issue does not name specific files, tests, or entry points. Define the retry semantics and acceptance criteria for Pulsar consumption before implementation, then verify that the resulting middleware retries failed messages as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100