DOCSP-18342: Source Connector Kafka topic config (#140)

* DOCSP-18342: Source Connector Kafka topic config

Author: Chris Cho

source/source-connector/configuration-properties.txt

@@ -35,6 +35,9 @@ See the following categories for a list of related configuration properties:
    * - :ref:`MongoDB Connection Properties <source-configuration-mongodb-connection>`
      - Specify how to connect to your MongoDB cluster.
 
+   * - :ref:`Kafka Topic Properties <source-configuration-change-stream>`
+     - Specify which topics to publish change stream data.
+
    * - :ref:`Change Stream Properties <source-configuration-change-stream>`
      - Specify your change stream pipelines and cursor settings.
 
@@ -46,9 +49,9 @@ See the following categories for a list of related configuration properties:
    :caption: Sink Connector Configuration Properties
 
    MongoDB Connection </source-connector/configuration-properties/mongodb-connection>
-   Change Stream Properties </source-connector/configuration-properties/change-stream>
+   Kafka Topic </source-connector/configuration-properties/kafka-topic>
+   Change Stream </source-connector/configuration-properties/change-stream>
 
 ..
    - Document/Data Format
-   - Kafka Topic
    - Error Handling and Resume Options

source/source-connector/configuration-properties/change-stream.txt

@@ -95,28 +95,6 @@ Settings
        | **Default**: ``""``
        | **Accepted Values**: A valid collation JSON document
 
-   * - | **copy.existing.pipeline**
-     - | **Type:** string
-       |
-       | **Description:**
-       | An array of :manual:`pipeline operations </core/aggregation-pipeline/>`
-         to run when copying existing data. You can use this setting to
-         improve the use of indexes by the copying manager to make the copying
-         process more efficient.
-
-       .. example::
-
-          The following example shows how you can use the :manual:`$match </reference/operator/aggregation/match/>`
-          aggregation operator to copy only documents that contain a
-          ``closed`` field with a value of ``false``.
-
-          .. code-block:: none
-
-             copy.existing.pipeline=[ { "$match": { "closed": "false" } } ]
-
-       | **Default**: ``[]``
-       | **Accepted Values**: Valid aggregation pipeline stages
-
    * - | **batch.size**
      - | **Type:** int
        |

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

@@ -0,0 +1,109 @@
+======================
+Kafka Topic Properties
+======================
+
+.. default-domain:: mongodb
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 2
+   :class: singlecol
+
+Overview
+--------
+
+Use the following configuration settings to specify which Kafka topics the
+source connector should publish data to.
+
+.. include:: /includes/source-config-link.rst
+
+Settings
+--------
+
+.. list-table::
+   :header-rows: 1
+   :widths: 35 65
+
+   * - Name
+     - Description
+
+   * - | **topic.prefix**
+     - | **Type:** string
+       |
+       | **Description:**
+       | The prefix to prepend to database and collection names to
+         generate the name of the Kafka topic on which to publish the data.
+
+       .. seealso::
+
+          :ref:`Topic Naming Prefix Usage Example <source-usage-example-topic-naming>`
+
+       | **Default**: ""
+       | **Accepted Values**: A string composed of ASCII alphanumeric
+         characters including ".", "-", and "_"
+
+   * - | **topic.suffix**
+     - | **Type:** string
+       |
+       | **Description:**
+       | The suffix to append to database and collection names to
+         generate the name of the Kafka topic on which to publish the data.
+
+       .. seealso::
+
+          :ref:`Topic Naming Suffix Usage Example <source-usage-example-topic-naming>`
+
+       | **Default**: ""
+       | **Accepted Values**: A string composed of ASCII alphanumeric
+         characters including ".", "-", and "_"
+
+   * - | **topic.namespace.map**
+     - | **Type:** string
+       |
+       | **Description:**
+       | Specifies a JSON mapping between change stream document namespaces
+         and topic names.
+
+       .. example::
+
+          The following mappings instruct the connector to do the following:
+
+          - 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.
+
+          .. code-block:: properties
+             :copyable: false
+
+             topic.namespace.map={"myDb": "topicOne", "myDb.myColl\": "topicTwo"}
+
+       | 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:
+
+          .. code-block:: properties
+             :copyable: false
+
+             topic.namespace.map={"*": "topicThree"}
+
+       | **Default**: ""
+       | **Accepted Values**: A valid JSON object
+
+   * - | **topic.mapper**
+     - | **Type:** string
+       |
+       | **Description:**
+       | The Java class that defines your custom topic mapping logic.
+       |
+       | **Default**: ``com.mongodb.kafka.connect.source.topic.mapping.DefaultTopicMapper``
+       | **Accepted Values**: Valid full class name of an implementation
+         of the `TopicMapper <https://github.com/mongodb/mongo-kafka/blob/master/src/main/java/com/mongodb/kafka/connect/source/topic/mapping/TopicMapper.java>`__
+         class.
+
+

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

@@ -1,3 +1,5 @@
+.. _source-usage-example-topic-naming:
+
 ============
 Topic Naming
 ============