-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
io.debezium.util.Threads class is designed to work with SourceConnector, but there is use case where we want to utilize it within a ChangeConsumer context.
Bug report
This to to fix the bug reported here.
https://issues.redhat.com/browse/DBZ-7904
What Debezium connector do you use and what version?
2.5
What is the connector configuration?
debezium.sink.type=pubsub
What is the captured database version and mode of depoyment?
N/A
What behaviour do you expect?
Threads is util class providing threadFactory and executors, currently can be utilized only in one source connector. Though it should be generic.
What behaviour do you see?
Threads is util class providing threadFactory and executors, currently can be utilized only in one source connector.
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
N/A
How to reproduce the issue using our tutorial deployment?
N/A
Feature request or enhancement
Enhancing the utility of the Threads class by making it more generic would be beneficial. Currently, it provides ThreadFactory and Executors that are tailored for use in one of source connectors. By refactoring it to be more generic, it could serve the purposes across different contexts.
Which use case/requirement will be addressed by the proposed feature?
https://github.com/debezium/debezium-server/pull/95/files
Implementation ideas (optional)
- links to
-
RHEA-2024:139598 Red Hat build of Debezium 2.5.4 release