-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
2.3.0-beta1
What is the connector configuration?
.with(CommonConnectorConfig.SIGNAL_ENABLED_CHANNELS, FileSignalChannel.class)
.with(FileSignalChannel.SIGNAL_FILE, "/tmp/signal.txt")
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
self-hosted mysql
What behaviour do you expect?
FileSignalChannel to be loaded
What behaviour do you see?
FileSignalChannel is not loaded
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
<Your answer>
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
<Your answer>
How to reproduce the issue using our tutorial deployment?
Try to use a File-based signal
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
io.debezium.pipeline.signal.channels.SourceSignalChannel
io.debezium.pipeline.signal.channels.KafkaSignalChannel
This should also include the FileSignalChannel.
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release