Move the Debezium data package to the API project [DBZ-5222]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-5222](https://issues.redhat.com/browse/DBZ-5222)
Right now projects that need to interact with logical Debezium types (like io.debezium.data.VariableScaleDecimal) have no choice but to import the entire debezium-core project which is quite hefty.
It might be better in the long term for these classes to reside in the API package, so that there can be a more minimal artifact. For comparison, classes like org.apache.kafka.connect.data.Timestamp in Kafka Connect are in the API package.
Contributor guide
Research direction
Start by locating the Debezium data package, the API project, and the current debezium-core dependency path for logical types such as VariableScaleDecimal. Compare the arrangement with Kafka Connect API types, then determine the dependency and compatibility implications. Done means consumers can use these types from a smaller API artifact without importing the entire core project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100