From 896f1440db50fa23f3092025b97d40c0b4e13259 Mon Sep 17 00:00:00 2001 From: Bob Roldan Date: Fri, 4 Mar 2022 18:20:00 -0500 Subject: [PATCH] DBZ-4655 Modify link formats to fix build errors --- documentation/modules/ROOT/pages/configuration/avro.adoc | 2 +- documentation/modules/ROOT/pages/connectors/db2.adoc | 2 +- documentation/modules/ROOT/pages/connectors/sqlserver.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/modules/ROOT/pages/configuration/avro.adoc b/documentation/modules/ROOT/pages/configuration/avro.adoc index 7f9e763fc..f0a6f304d 100644 --- a/documentation/modules/ROOT/pages/configuration/avro.adoc +++ b/documentation/modules/ROOT/pages/configuration/avro.adoc @@ -23,7 +23,7 @@ For each change event record, the {prodname} connector completes the following a You can specify converters for each individual {prodname} connector instance. Kafka Connect provides a JSON converter that serializes the record keys and values into JSON documents. The default behavior is that the JSON converter includes the record's message schema, which makes each record very verbose. -The xref:{link-tutorial}[{name-tutorial}] shows what the records look like when both payload and schemas are included. +The {link-prefix}:{link-tutorial}[{name-tutorial}] shows what the records look like when both payload and schemas are included. If you want records to be serialized with JSON, consider setting the following connector configuration properties to `false`: * `key.converter.schemas.enable` diff --git a/documentation/modules/ROOT/pages/connectors/db2.adoc b/documentation/modules/ROOT/pages/connectors/db2.adoc index dc0853689..063972617 100644 --- a/documentation/modules/ROOT/pages/connectors/db2.adoc +++ b/documentation/modules/ROOT/pages/connectors/db2.adoc @@ -2305,7 +2305,7 @@ The {prodname} Db2 connector provides three types of metrics that are in additio * xref:{link-db2-connector}#db2-streaming-metrics[Streaming metrics] provide information about connector operation when the connector is capturing changes and streaming change event records. * xref:{link-db2-connector}#db2-schema-history-metrics[Schema history metrics] provide information about the status of the connector's schema history. -xref:{link-debezium-monitoring}[{prodname} monitoring documentation] provides details for how to expose these metrics by using JMX. +{link-prefix}:{link-debezium-monitoring}#monitoring-debezium[{prodname} monitoring documentation] provides details for how to expose these metrics by using JMX. // Type: reference // ModuleID: monitoring-debezium-during-snapshots-of-db2-databases diff --git a/documentation/modules/ROOT/pages/connectors/sqlserver.adoc b/documentation/modules/ROOT/pages/connectors/sqlserver.adoc index cfc83f2de..01d77f592 100644 --- a/documentation/modules/ROOT/pages/connectors/sqlserver.adoc +++ b/documentation/modules/ROOT/pages/connectors/sqlserver.adoc @@ -2614,7 +2614,7 @@ The connector provides the following metrics: * xref:sqlserver-streaming-metrics[Streaming metrics] for monitoring the connector when reading CDC table data. * xref:sqlserver-schema-history-metrics[Schema history metrics] for monitoring the status of the connector's schema history. -For information about how to expose the preceding metrics through JMX, see the xref:{link-debezium-monitoring}[{prodname} monitoring documentation]. +For information about how to expose the preceding metrics through JMX, see the {link-prefix}:{link-debezium-monitoring}#monitoring-debezium[{prodname} monitoring documentation]. // Type: reference // ModuleID: debezium-sqlserver-connector-snapshot-metrics