Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-8738

Correlation ID is unset before sending aborted notification

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.1.0.Beta1
    • None
    • core-library
    • None
    • Moderate

      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?

      Latest

      What is the connector configuration?

      Mysql connector

      What is the captured database version and mode of deployment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      Mysql 8

      What behavior do you expect?

      Correlation id to be sent in aborted notification of incremental snapshot.

      What behavior do you see?

      Randomly generated id sent back in aborted notification.

      Do you see the same behaviour using the latest released Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      Yes

              Unassigned Unassigned
              mejiadaniel2021 Daniel Mejia
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: