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`
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.
* Update Db2 connector instructions for accuracy/consistency
* Updates for consistency with other connector documentation
* Remove downstream ModuleID declaration for properties topic
* Grammar correction
* Update link text
* Add missing space
* Refactor conditionalized content so downstream builds correctly
* Update MySQL connector doc with common corrections
* Remove downstream ModuleID declaration for properties topic
* Adjust link text
* Modify xrefs in product content
* Add missing space
* Reconfigure conditionals to correct downstream build errors
* Refactor conditional content to get expected downstream results
* Add passage about immutable containers and OpenShift deployment
* Fix incorrect acronym expansion;remove {zwsp} in table entry
* Restructure, update deploy steps based on PG version
* Remove dup text. Adjust head levels to fix Antora build errors
* Redefine conditional boundaries + downstream style/format fixes
* Set subs="+attributes" on code block to permit value to render
* Remove ModuleID declaration that breaks link to snapshot topic
* Update deployment topic for consistency w/ other connectors
* Refactoring to restore missing conditional content downstream
Adds a new "sequence" field to all sources via the AbstractSourceInfo
class. Specifically, this field is required to deduplicate records
from PostgreSQL sources in O(1) time. The sequence field is a stringified
list of metadata. For PostgreSQL sources, this will include the last
committed LSN and the current LSN. For other sources, this will be NULL
until implemented. A new integration test was added for PostgreSQL.
* Use {debezium-version} variable in examples
* Correct typos
* Document non-support for CLOB/BLOB data types
* Fix rendering of <= with unicode character
* Moved XStream documentation into separate section
* Moved database.oracle.version to internal
* Removed reference to database.oracle.version
* Resolve XStream POS version from OracleDatabaseVersion as fallback
when internal.database.oracle.version is not supplied.
* Default value `0` disables the check
* Any negative value will show a configuration problem
* Any positive value over `0` will enable the retention check
