anchor.diff:  For example, if the `mongodb.user` property is not set, but the connection string includes the MongoDB username, the connector reads the information from the string.
   ====
   
  -|[[mongodb-property-mongodb-name]]<<mongodb-property-mongodb-name, `+mongodb.name+`>>
  +|[[mongodb-property-topic-prefix]]<<mongodb-property-topic-prefix, `+topic.prefix+`>>
   |No default
   |A unique name that identifies the connector and/or MongoDB replica set or sharded cluster that this connector monitors.
   Each server should be monitored by at most one {prodname} connector, since this server name prefixes all persisted Kafka topics emanating from the MongoDB replica set or cluster.
  
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:   "config": {
      "connector.class": "io.debezium.connector.mongodb.MongoDbConnector", // <2>
      "mongodb.hosts": "rs0/192.168.99.100:27017", // <3>
      "topic.prefix": "fullfillment", // <4>
      "collection.include.list": "inventory[.]*" // <5>
    }
  }
  