DOCSP-18679: ia-v2 v1.5 branch DOT NOT MERGE (#198)

* DOCSP-18679: ia-v2 v1.5 branch

Author: Chris Cho

config/redirects

@@ -18,3 +18,7 @@ raw: kafka-connector/ -> ${base}/current/
 [*-master]: kafka-connector/${version}/kafka-sink-postprocessors/ -> ${base}/${version}/fundamentals/post-processors/
 [*-master]: kafka-connector/${version}/kafka-sink-time-series-example/ -> ${base}/${version}/tutorials/migrate-time-series/
 [*-master]: kafka-connector/${version}/kafka-connect-migration/ -> ${base}/${version}/
+
+[*-v1.5]: kafka-connector/${version}/tutorials/migrate-time-series/ -> ${base}/${version}/
+[*-v1.5]: kafka-connector/${version}/sink-connector/configuration-properties/time-series/ -> ${base}/${version}/
+

snooty.toml

@@ -11,9 +11,8 @@ kc = "Kafka Connect"
 avro = "Apache Avro"
 avro-short = "Avro"
 kafka-connect = "Confluent Kafka Connect"
-connector_version="1.6"
-connector_driver_version="4.3"
+connector_version="1.5"
+connector_driver_version="4.2"
 sink-connector="MongoDB Kafka sink connector"
 source-connector="MongoDB Kafka source connector"
-connector_driver_url_base="https://docs.mongodb.com/drivers/java/sync/v{+connector_driver_version+}/"
 pipeline-size = "2.4 GB"

source/introduction/connect.txt

@@ -61,7 +61,7 @@ to interact with MongoDB.
    {+connector_driver_version+} of the MongoDB Java driver.
 
 To learn what connection URI options are available in the {+mkc+}, see
-`the MongoDB Java driver Connection guide <{+connector_driver_url_base+}fundamentals/connection/#connection-options>`__.
+`the MongoDB Java driver Connection tutorial <https://mongodb.github.io/mongo-java-driver/4.2/driver/tutorials/connect-to-mongodb/>`__.
 
 Authentication
 ~~~~~~~~~~~~~~
@@ -84,7 +84,7 @@ The following is an example of a connection URI that authenticates with MongoDB
    `the Externalize Secrets guide from Confluent <https://docs.confluent.io/platform/current/connect/security.html#externalizing-secrets>`__. 
 
 To learn what authentication mechanisms are available, see
-`the MongoDB Java driver Authentication Mechanisms guide <{+connector_driver_url_base+}fundamentals/auth/#mechanisms>`__.
+`the MongoDB Java driver Authentication tutorial <https://mongodb.github.io/mongo-java-driver/4.2/driver/tutorials/authentication/>`__.
 
 To learn more about authentication in the {+mkc+}, see the
 :doc:`Security and Authentication guide </security-and-authentication>`.

source/sink-connector/configuration-properties.txt

@@ -67,10 +67,6 @@ See the following categories for a list of related configuration properties:
    * - :doc:`Change Data Capture Properties </sink-connector/configuration-properties/cdc>`
      - Specify how the connector captures CDC events from a Kafka topic.
 
-   * - :doc:`Time Series Properties </sink-connector/configuration-properties/time-series>`
-     - Configure the connector to sink data to a MongoDB time series
-       collection.
-
 See the `Confluent Sink Connector documentation <https://docs.confluent.io/current/installation/configuration/connect/sink-connect-configs.html>`__
 for more information on these settings.
 
@@ -87,5 +83,4 @@ for more information on these settings.
    Write Model Strategy <sink-connector/configuration-properties/write-strategies>
    Topic Override <sink-connector/configuration-properties/topic-override>
    Change Data Capture <sink-connector/configuration-properties/cdc>
-   Time Series <sink-connector/configuration-properties/time-series>
 

source/sink-connector/configuration-properties/error-handling.txt

@@ -30,45 +30,6 @@ Settings
    * - Name
      - Description
 
-   * - | **mongo.errors.tolerance**
-     - | **Type:** string
-       |
-       | **Description:**
-       | Whether to continue processing messages if the connector encounters
-         an error.
-       | When set to ``none``, the connector reports any error and
-         blocks further processing of the rest of the messages.
-       | When set to ``all``, the connector ignores any problematic messages.
-
-       .. note::
-
-          This property overrides the `errors.tolerance <https://docs.confluent.io/platform/current/installation/configuration/connect/sink-connect-configs.html#errors-tolerance>`__
-          property of the Connect Framework.
-
-       | **Default:** ``"none"``
-       | **Accepted Values**: ``"none"`` or ``"all"``
-
-   * - | **mongo.errors.log.enable**
-     - | **Type:** boolean
-       |
-       | **Description:**
-       | Whether the connector should write details of errors including 
-         failed operations to the log file. The connector classifies
-         errors as "tolerated" or "not tolerated" using the 
-         ``errors.tolerance`` or ``mongo.errors.tolerance`` settings.
-
-       | When set to ``true``, the connector logs both "tolerated" and
-         "not tolerated" errors.
-       | When set to ``false``, the connector logs "not tolertaed" errors.
-
-       .. note::
-
-          This property overrides the `errors.log.enable <https://docs.confluent.io/platform/current/installation/configuration/connect/sink-connect-configs.html#errors-log-enable>`__
-          property of the Connect Framework.
-
-       | **Default:** ``false``
-       | **Accepted Values**: ``true`` or ``false``
-
    * - | **errors.log.include.messages**
      - | **Type:** boolean
        |
@@ -136,8 +97,8 @@ the dead letter queue messages should include context headers.
 
 .. code-block:: properties
 
-   mongo.errors.tolerance=all
-   mongo.errors.log.enable=true
+   errors.tolerance=all
+   errors.log.enable=true
    errors.log.include.messages=true
    errors.deadletterqueue.topic.name=example.deadletterqueue
    errors.deadletterqueue.context.headers.enable=true

source/sink-connector/configuration-properties/mongodb-connection.txt

@@ -61,45 +61,3 @@ Settings
        | **Default**: ``5000``
        | **Accepted Values**: An integer
 
-   * - **server.api.version**
-     - | **Type:** string
-       |
-       | **Description:**
-       | The Versioned API version you want to use with your MongoDB
-         server. For more information on the Versioned API and versions of
-         the server that support it, see the :manual:`Versioned API </reference/versioned-api/>`
-         MongoDB server manual guide.
-       |
-       | **Default**: ``""``
-       | **Accepted Values**: An empty string or a valid Versioned API version.
-
-   * - **server.api.deprecationErrors**
-     - | **Type:** boolean
-       |
-       | **Description:**
-       | When set to ``true``, if the connector calls a command on your
-         MongoDB instance that's deprecated in the declared Versioned API
-         version, it raises an exception.
-       | You can set the API version with the ``server.api.version``
-         configuration option. For more information on the Versioned API, see
-         the MongoDB manual entry on the
-         :manual:`Versioned API </reference/versioned-api/>`.
-       |
-       | **Default**: ``false``
-       | **Accepted Values**: ``true`` or ``false``
-
-   * - **server.api.strict**
-     - | **Type:** boolean
-       |
-       | **Description:**
-       | When set to ``true``, if the connector calls a command on your
-         MongoDB instance that's not covered in the declared Versioned API
-         version, it raises an exception.
-       | You can set the API version with the ``server.api.version``
-         configuration option. For more information on the Versioned API, see
-         the MongoDB manual entry on the
-         :manual:`Versioned API </reference/versioned-api/>`.
-       |
-       | **Default**: ``false``
-       | **Accepted Values**: ``true`` or ``false``
-

source/sink-connector/configuration-properties/time-series.txt

@@ -52,7 +52,7 @@ when it encounters an error. This is a good option for you if any error in
 your sink connector indicates a serious problem.
 
 When your sink connector crashes, you must do one of the
-following actions and then restart your connector to resume processing messages: 
+following actions and then restart your connector to resume processing messages:
 
 - Allow your sink connector to temporarily :ref:`tolerate errors <kafka-sink-tolerate-errors>`
 - Update your sink connector's configuration to allow it to process the message
@@ -73,7 +73,7 @@ Tolerate All Errors
 
 You can configure your sink connector to tolerate all errors and never stop
 processing messages. This is a good option for getting your sink connector up and
-running quickly, but you run the risk of missing problems in your connector 
+running quickly, but you run the risk of missing problems in your connector
 as you do not receive any feedback if something goes wrong.
 
 You can have your sink connector tolerate all errors by specifying the following
@@ -88,7 +88,7 @@ option:
 Write Errors and Errant Messages to a Topic
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can configure your sink connector to write errors and errant messages to a 
+You can configure your sink connector to write errors and errant messages to a
 topic, called a **dead letter queue**, for you to inspect or process further.
 A dead letter queue is a location in message queueing
 systems such as {+ak+} where the system routes errant messages instead of
@@ -111,24 +111,12 @@ errant message, use the following option:
 
    errors.deadletterqueue.context.headers.enable=true
 
-.. important:: Bulk Write Errors 
+.. warning:: Bulk Write Errors
 
-   If an error occurs while performing a bulk write to MongoDB, you must specify
-   the following to log any information about the error to a dead letter queue:
+   You cannot configure the connector to write bulk write errors to the
+   dead letter queue.
 
-   .. code-block:: properties
-
-      errors.tolerance=all
-      mongo.errors.tolerance=none
-      errors.deadletterqueue.topic.name=<name of topic to use as dead letter queue>
-
-   We will fix this special case soon. To track the status of this issue, 
-   see :issue:`this JIRA ticket <KAFKA-223>`.
-
-   For more information on the ``mongo.errors.tolerance`` option, see our
-   section on :ref:`connector level options <kakfa-sink-connector-level>`.
-
-For more information, see Confluent's guide on 
+For more information, see Confluent's guide on
 `Dead Letter Queues <https://docs.confluent.io/cloud/current/connectors/dead-letter-queue.html#dead-letter-queue>`__.
 
 To view another dead letter queue configuration example, see :ref:`<sink-dead-letter-queue-configuration-example>`.
@@ -169,34 +157,6 @@ topic and offset, use the following option:
 
    errors.log.include.messages=true
 
-For more information, see Confluent's guide on 
+For more information, see Confluent's guide on
 `logging with Kafka Connect <https://docs.confluent.io/platform/current/connect/logging.html>`__.
 
-.. _kakfa-sink-connector-level:
-
-Handle Errors at the Connector Level
-------------------------------------
-
-The {+mkc+} provides options that allow you to configure error
-handling at the connector level. The options are as follows:
-
-.. list-table::
-   :header-rows: 1
-   :widths: 50 50
-
-   * - Kafka Connect Option
-     - {+mkc+} Option
-
-   * - ``errors.tolerance`` 
-     - ``mongo.errors.tolerance``
-
-   * - ``errors.log.enable``
-     - ``mongo.errors.log.enable``
-
-You want to use these options if you want your connector to respond differently
-to errors related to MongoDB than to errors related to the {+kc+} framework. 
-
-For more information, see the following resources:  
-
-- :ref:`<sink-configuration-error-handling>`
-- :issue:`New Names for Error Tolerance Options JIRA Ticket <KAFKA-215>`