Links to the Transaction metadata topic from the property table descriptions for the provide.transaction.metadata property are broken in the downstream RHIQ3-2021 version of the docs for several connectors. The links are broken in the following connector docs, because they incorrectly target the upstream anchor ID vs. the downstream ModuleIDs:
- Db2 (
FIXED in 2022.Q1
): Properties table link targets db2-transaction-metadata.-
The correct downstream link target is debezium-db2-connector-generated-events-that-represent-transaction-boundaries
- MongoDB (ref-mongodb-connector-properties.adoc): Properties table link targets mongodb-transaction-metadata- FIXED in 2022.Q1
The correct downstream link target is debezium-mongodb-connector-generated-events-that-represent-transaction-boundaries
FIXED in 2022.Q1
): Required properties table link targets oracle-transaction-metadata.-
The correct downstream link target is debezium-oracle-connector-generated-events-that-represent-transaction-boundaries
- SQL Server (ref-descriptions-of-debezium-sql-server-connector-configuration-properties.adoc): Advanced SQL Server connector configuration properties link targets sqlserver-transaction-metadata.- FIXED in 2022.Q1
The correct downstream link target is debezium-sql-server-connector-generated-events-that-represent-transaction-boundaries
The links work downstream for MySQL, because the upstream and downstream IDs are identical.
The links work for PG because they were manually updated downstream to replace the anchor ID with the ModuleID.
- is related to
DBZ-3961 Update docs to specify that connectors track metadata only for transactions that occur after deployment