anchor.diff:  ----
   
   Unless overridden via the xref:{link-mongodb-connector}#mongodb-property-topic-transaction[`topic.transaction`] option,
  -transaction events are written to the topic named xref:mongodb-property-mongodb-name[`_<mongodb.name>_`]`.transaction`.
  +transaction events are written to the topic named xref:mongodb-property-topic-prefix[`_<topic.prefix>_`]`.transaction`.
   
   .Change data event enrichment
   When transaction metadata is enabled, the data message `Envelope` is enriched with a new `transaction` field.
  
positive.code: === Topic names
  
  The MongoDB connector writes events for all insert, update, and delete operations to documents in each collection to a single Kafka topic.
  The name of the Kafka topics always takes the form _logicalName_._databaseName_._collectionName_, where _logicalName_ is the xref:{link-mongodb-connector}#mongodb-logical-connector-name[logical name] of the connector as specified with the `mongodb.name` configuration property, _databaseName_ is the name of the database where the operation occurred, and _collectionName_ is the name of the MongoDB collection in which the affected document existed.
  
  For example, consider a MongoDB replica set with an `inventory` database that contains four collections: `products`, `products_on_hand`, `customers`, and `orders`.
  If the connector monitoring this database were given a logical name of `fulfillment`, then the connector would produce events on these four Kafka topics:
  
negative.code:     class: io.debezium.connector.mongodb.MongoDbConnector // <2>
      config:
       mongodb.hosts: rs0/192.168.99.100:27017 // <3>
       topic.prefix: fulfillment // <4>
       collection.include.list: inventory[.]* // <5>
  ----
  <1> The name that is used to register the connector with Kafka Connect.
  