-
Enhancement
-
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?
latest version
What is the connector configuration?
Any configuration
What behaviour do you see?
Currently in all the offsets for the connector irrespective of which phase it is in, there is an attribute `transaction_id` which is present. This is null in most of the cases, since it's set only when `provide.transaction.metadata` config is set.
What behaviour do you expect?
Ideally this field should be populated only when it has some value to it. Otherwise it creates a confusion, even though the offset is of an open transaction, the `transaction_id` would be null.
Do you see the same behaviour using the latest released Debezium version?
yes
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)
This field should be populated only on non-null values for transaction id.
- links to
-
RHEA-2024:139598 Red Hat build of Debezium 2.5.4 release