-
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:
PostgresSnapshotChangeEventSource#complete is invoking Snapshotter#snapshotCompleted here regardless of snapshot result.
Snapshotter#snapshotCompleted() doesn't have snapshot result. So it shouldn't called when snapshot is failed/aborted.
What Debezium connector do you use and what version?
2.0.0.Final
What is the connector configuration?
N/A
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
N/A
What behaviour do you expect?
Snapshotter#snapshotCompleted() doesn't have snapshot result. So, it should be called when snapshot is successful.
What behaviour do you see?
Snapshotter#snapshotCompleted() is called regardless of snapshot result.
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes.
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
N/A
How to reproduce the issue using our tutorial deployment?
N/A
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)
<Your answer>
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release