The inclusion of two consecutive anchor links breaks processing when files are fetched and split for downstream use. Testing downstream shows that rather than deleting the second anchor ID `[[mongodb-tailing-the-oplog]]` that is associated with the heading *Streaming changes*, move it to follow the heading.
Also inserted missing `debezium` string into the anchor ID in the downstream xref that links to `default-names-of-kafka-topics-that-receive-debezium-mongodb-change-event-records`
Removed comments added to the head of the file that incorrectly duplicate downstream file metadata from another file. The erroneous comments result in an incorrect file being generated when content from the repo is fetched downstream.
This change has no effect on the content that is rendered upstream
Updates a cross-reference in the content that is conditionalized for the product build to target the correct downstream anchor ID. This change applies a change that was previously applied manually to the downstream documentation. There is no effect on the content that is rendered upstream.
Hello,
First, thanks for making this project open source. It is such a great piece of software.
While I was playing with it and try to configure a mongodb connector, I noticed that the json example to configure a mongodb connector is not valid. There is an unnecessary comma at the end of the payload.
Here is a minor contribution that could help and could save some time for the future users.
Restore the downstream comment in postgresql.adoc that specifies the downstream anchor ID for the configuration properties topic. I previously removed the comment while troubleshooting downstream linking errors. A tooling change should address this deficit without requiring us to always use the upstream anchor IDs.
This change is not visible in either the upstream or downstream content and has no effect on the upstream behavior.
In sqlserver.adoc, restore the downstream comment that specifies the downstream anchor ID for the snapshots topic. I previously removed the comment, because downstream, links to the topic were not working. A tooling change should address this deficit without requiring us to use the upstream anchor IDs.
This change is not visible in either the upstream or downstream content and has no effect on the upstream behavior.
In the mysql.adoc, restore the downstream comment that specifies the downstream anchor ID for the snapshots topic. I previously removed the comment, because downstream, links to the topic were not working. A tooling change should address this deficit without requiring us to use the upstream anchor IDs.
This change is not visible in either the upstream or downstream content and it has no effect on the upstream behavior.
Restore the downstream comment that specifies the downstream anchor ID for the snapshots topic. I previously removed the comment, because downstream, links to the topic were not working. A tooling change should address this deficit without requiring us to remove further ModuleIDs.
This change is not visible in either the upstream or downstream content and has no effect on the upstream behavior.
Restore the ModuleID declaration `descriptions-of-debezium-db2-connector-configuration-properties` that is used for the for the connector properties topic downstream and which was removed as part of the recent user guide update for the Db2 connector in DBZ-3298.
Previously, I removed the downstream ModuleID declaration for the Connector properties topic on L1947 because of a linking problem. I now believe that the problem resulted from errors in the way that the downstream content was structured, so I've restored the Module ID and the link to it on L1642.
