[Enhancement] RecordPosition persistence and reading, integrated with Registry
- 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
At present, RecordPosition contains the offset information of ConnectorRecord. In the scenario of high availability of connector and avoiding repeated consumption, it needs to be persisted and read the latest event consumption position when the poll method is executed on the source connector side.
### Describe the solution you'd like
Implement the registry under the eventmesh-openconnect module, which can realize the memory mode or file mode as the default usage mode, integrate the eventmesh-meta-api module, and use etcd as the registry plugin.
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by examining the eventmesh-openconnect module and the eventmesh-meta-api integration described in the issue. Determine how source connector poll operations expose RecordPosition and how a registry could support memory and file modes before considering the etcd plugin. Done means the latest consumption position is persisted and read for high-availability connector operation without repeated consumption.
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