Follow-up tasks around Redis offset storage [DBZ-4816]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-4816](https://issues.redhat.com/browse/DBZ-4816)
There's a few things which should be improved after the initial work on this offset storage implementation (via DBZ-4509):
* Move the implementation into a separate module so it can be used solely with Debezium Engine, but without Debezium Server
* Investigate why the scope of the PG connector dependency had to be changed to "runtime" rather than "test" (see discussion in [PR 3220|https://github.com/debezium/debezium/pull/3220])
* Move to contract independent of Kafka Connect once available (see DBZ-1971)
Contributor guide
Research direction
Start by reading the initial implementation from DBZ-4509 and the dependency discussion in PR 3220. Review DBZ-1971 before assessing the Kafka Connect contract; done means the implementation is isolated for Debezium Engine use, the PG dependency scope is explained or corrected, and the contract migration is addressed when available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100