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

Fix inconsistent transaction id when handling transactional messages in Vitess connector


      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?

      Vitess 1.9.0.CR1

      What is the connector configuration?

      provide.transaction.metadata = true

      What is the captured database version and mode of depoyment?

      Vitess 12.0. Local docker, and Kubernetes on AWS.

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

      What behaviour do you expect?

      All row events and transaction medatadata should have correct transaction IDs

      What behaviour do you see?

      Some row events and transaction metadata have the wrong transaction ID (obviously reuse the transaction IDs from previous events)

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


      Do you have the connector logs, ideally from start till finish?

      See PR: https://github.com/debezium/debezium-connector-vitess/pull/79

      How to reproduce the issue using our tutorial deployment?

      See PR: https://github.com/debezium/debezium-connector-vitess/pull/79

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      Downstream consumers that rely on transaction metadata and their transaction ID to aggregate corresponding row events in between.

      Implementation ideas (optional)

      See PR: https://github.com/debezium/debezium-connector-vitess/pull/79

            Unassigned Unassigned
            shichaoan Shichao An
            0 Vote for this issue
            3 Start watching this issue