anchor.diff:  endif::community[]
   
   |[[mongodb-property-skipped-operations]]<<mongodb-property-skipped-operations, `+skipped.operations+`>>
  -|
  +|No default
   | comma-separated list of operation types that will be skipped during streaming.
   The operations include: `c` for inserts/create, `u` for updates, and `d` for deletes.
   By default, no operations are skipped.
   
   |[[mongodb-property-snapshot-collection-filter-overrides]]<<mongodb-property-snapshot-collection-filter-overrides, `+snapshot.collection.filter.overrides+`>>
  -|
  +|No default
   | Controls which collection items are included in snapshot. This property affects snapshots only. Specify a comma-separated list of collection names in the form _databaseName.collectionName_.
   
   For each collection that you specify, also specify another configuration property: `snapshot.collection.filter.overrides._databaseName_._collectionName_`. For example, the name of the other configuration property might be: `snapshot.collection.filter.overrides.customers.orders`. Set this property to a valid filter expression that retrieves only the items that you want in the snapshot. When the connector performs a snapshot, it retrieves only the items that matches the filter expression.
  
positive.code: |Property |Default |Description
  
  |[[mongodb-property-name]]<<mongodb-property-name, `+name+`>>
  |
  |Unique name for the connector. Attempting to register again with the same name will fail. (This property is required by all Kafka Connect connectors.)
  
  |[[mongodb-property-connector-class]]<<mongodb-property-connector-class, `+connector.class+`>>
  |
  |The name of the Java class for the connector. Always use a value of `io.debezium.connector.mongodb.MongoDbConnector` for the MongoDB connector.
  
  |[[mongodb-property-mongodb-hosts]]<<mongodb-property-mongodb-hosts, `+mongodb.hosts+`>>
  |
  |The comma-separated list of hostname and port pairs (in the form 'host' or 'host:port') of the MongoDB servers in the replica set. The list can contain a single hostname and port pair. If `mongodb.members.auto.discover` is set to `false`, then the host and port pair should be prefixed with the replica set name (e.g., `rs0/localhost:27017`). +
   +
  [NOTE]
  
negative.code: ====
  
  |[[mongodb-property-mongodb-connection-string]]<<mongodb-property-mongodb-connection-string, `+mongodb.connection.string+`>>
  |No default
  |Specifies a connection string that the connector uses during the initial discovery of a MongoDB replica set.
  To use this option, you must set the value of `mongodb.members.auto.discover` to `true`.
  You cannot use this property together with the `mongodb.hosts` property. +
   +
  [NOTE]
  ====
  The connector uses this connection string during the initial replica set discovery process only.
  During the discovery process, the connector ignores the values of other connection properties (`mongodb.hosts`, `mongodb.user`,`mongodb.password`, `mongodb.authsource`, SSL configuration properties, and so forth).
  After the discovery process, when the connector attempts to establish a direct connection to a primary replica set member, it returns to using the standard connection properties,
  unless `mongodb.connection.string` specifies credential information that is otherwise undefined in the previously mentioned connection properties (for example, `mongodb.user`).
  
  ====
  
  |[[mongodb-property-mongodb-name]]<<mongodb-property-mongodb-name, `+mongodb.name+`>>
  |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.
  Use only alphanumeric characters, hyphens, dots and underscores to form the name.
  