(DOCSP-20789) Namespace Fix (#235)

Author: biniona-mongodb

source/source-connector/configuration-properties/kafka-topic.txt

@@ -76,32 +76,50 @@ Settings
 
        .. example::
 
-          The following mappings instruct the connector to do the following:
+          The following mapping instructs the connector to perform the following
+          actions:
 
           - Publish change stream documents originating from the
-            ``myDb.myColl`` MongoDB collection to the ``topicTwo`` Kafka topic.
-          - Publish all other change stream documents originating from the
-            ``myDb`` MongoDB database to the ``topicOne`` Kafka topic.
+            ``myDb.myColl`` MongoDB collection to the ``topicOne`` Kafka topic.
+          - Publish change stream documents originating from the
+            ``myDb`` MongoDB database and a collection other than ``myColl``
+            to the Kafka topic ``topicTwo.<collectionName>``.
+          - Publish change stream documents originating from the ``myDb``
+            MongoDB database that do not bear a collection name to
+            the ``topicTwo`` Kafka topic.
 
           .. code-block:: properties
              :copyable: false
 
-             topic.namespace.map={"myDb": "topicOne", "myDb.myColl\": "topicTwo"}
+             topic.namespace.map={"myDb.myColl": "topicOne", "myDb": "topicTwo"}
+
+          The following examples show which topic the connector sends
+          different change stream documents to using the preceding mapping:
 
-       | You can use the "*" wildcard character to match change stream
+          - A change stream document originating from the ``myDb`` database
+            and the ``myColl`` collection publishes to the
+            ``topicOne`` topic.
+          - A change stream document originating from the ``myDb`` database
+            and the ``newColl`` collection publishes to the
+            ``topicTwo.newColl`` topic.
+          - A change stream document originating from dropping the
+            ``myDb`` database, which does not bear a collection name,
+            publishes to the ``topicTwo`` topic.
+
+       | You can use the ``"*"`` wildcard character to match change stream
          document namespaces.
 
        .. example::
 
           The following mapping instructs the connector to publish all change
-          stream document namespaces to the ``topicThree`` topic:
+          stream documents to the ``topicThree`` topic:
 
           .. code-block:: properties
              :copyable: false
 
              topic.namespace.map={"*": "topicThree"}
 
-       | **Default**: ""
+       | **Default**: ``""``
        | **Accepted Values**: A valid JSON object
 
    * - | **topic.separator**

source/source-connector/usage-examples/topic-naming.txt

@@ -110,7 +110,8 @@ mapping, the connector performs the following actions:
   the connector sets the destination to the  ``electricVehicles`` topic.
 - If the change event came from the database ``carDb`` and a collection
   other than ``ev``, the connector sets the destination to the
-  ``automobiles`` topic.
+  ``automobiles.<collectionName>``
+  topic.
 - If the change document came from any database other than ``carDb``, the
   connector sets the destination topic to the default namespace naming
   scheme.
@@ -135,4 +136,3 @@ namespaces without mappings.
 In the preceding wildcard example, the connector publishes change documents
 that originated from all databases other than ``carDb`` to the
 ``otherVehicles`` topic.
-