Evaluate if and how a ServiceLoader based implementation can be used to replace mapping of connector class names to identifiers / connector type names for the API / UI [DBZ-6950]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-6950](https://issues.redhat.com/browse/DBZ-6950)
Evaluate if and how a ServiceLoader based implementation can be used to replace mapping of connector class names to identifiers / connector type names for the API / UI in the `ConnectorDescriptor` class.
Evaluate if the isolated ClassLoader that Kafka Connect is using for Connect REST Extensions is capable of finding implementations coming from installed Debezium connectors.
Also: How to support non-Debezium connectors eventually?
Also: Is this complexity worth the effort and will this really generate stable identifiers for the UI / API (and schemas)?
based on this discussion: https://github.com/debezium/debezium/pull/4745#pullrequestreview-1615622554
Contributor guide
Research direction
Start with the ConnectorDescriptor class and the Kafka Connect REST Extensions isolated ClassLoader behavior. Review the linked discussion and determine whether installed Debezium and eventual non-Debezium connectors can be discovered reliably, whether identifiers remain stable for the API, UI, and schemas, and document whether the complexity is worthwhile.
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
- 20/100