Correlation ID is unset before sending aborted notification [DBZ-8738]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-8738](https://issues.redhat.com/browse/DBZ-8738)
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
h1. Bug report
For bug reports, provide this information, please:
h2. What Debezium connector do you use and what version?
Latest
h2. What is the connector configuration?
Mysql connector
h2. What is the captured database version and mode of deployment?
(E.g. on-premises, with a specific cloud provider, etc.)
Mysql 8
h2. What behavior do you expect?
Correlation id to be sent in aborted notification of incremental snapshot.
!image-2025-02-25-11-25-50-678.png!
h2.
What behavior do you see?
Randomly generated id sent back in aborted notification.
!image-2025-02-25-11-25-11-253.png!
h2. Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes
Contributor guide
Assessment
This issue has not been assessed yet.