Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOCSP-34887: v1.11.1 release #151

Merged
merged 5 commits into from
Dec 11, 2023
Merged

DOCSP-34887: v1.11.1 release #151

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8d8add3
DOCSP-34887: v1.11.1 release
Dec 11, 2023
b04e70e
replace jira role
Dec 11, 2023
b031256
add facet and keywords
Dec 11, 2023
aa225b6
fix error
Dec 11, 2023
ba91504
PRR fixes
Dec 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 34 additions & 12 deletions source/whats-new.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,16 @@ What's New
:depth: 1
:class: singlecol

.. facet::
:name: genre
:values: reference

.. meta::
:keywords: bug fix, features

Learn what's new by version:

* :ref:`Version 1.11.1 <kafka-connector-whats-new-1.11.1>`
* :ref:`Version 1.11 <kafka-connector-whats-new-1.11>`
* :ref:`Version 1.10.1 <kafka-connector-whats-new-1.10.1>`
* :ref:`Version 1.10 <kafka-connector-whats-new-1.10>`
Expand All @@ -29,6 +37,20 @@ Learn what's new by version:
* :ref:`Version 1.1 <kafka-connector-whats-new-1.1>`
* :ref:`Version 1.0 <kafka-connector-whats-new-1.0>`

.. _kafka-connector-whats-new-1.11.1:

What's New in 1.11.1
--------------------

- Fixed wildcard matching on partial field names in documents. To learn more
about this fix, see the `KAFKA-391 <https://jira.mongodb.org/browse/KAFKA-391>`__
JIRA issue.

- Fixed an issue in which a null pointer exception is thrown when the
connector attempts to log null values on configuration settings. To learn
more about this fix, see the `KAFKA-390 <https://jira.mongodb.org/browse/KAFKA-390>`__
JIRA issue.

.. _kafka-connector-whats-new-1.11:

What's New in 1.11
Expand All @@ -52,7 +74,7 @@ What's New in 1.11
connector adds keys of the deleted documents to the tombstone events.
When set to ``false``, the connector uses the resume token as the source key
for the tombstone events.

Because this property is set to ``true`` by
default, this might be a breaking change for some users. To learn more,
see the list of :ref:`Change Stream Properties <source-configuration-change-stream-list>`.
Expand All @@ -65,13 +87,13 @@ What's New in 1.10.1
--------------------

.. important:: Upgrade to Version 1.10.1
Version 1.9 introduced a bug related to ``MongoSourceTask.start`` that can cause a resource leak on
both the connector side and the server side .

Version 1.9 introduced a bug related to ``MongoSourceTask.start`` that can cause a resource leak on
both the connector side and the server side.

Upgrade to version 1.10.1 if you are using version 1.9 or 1.10 of the connector.

- Fixed a resource leak related to ``MongoSourceTask.start`` that was introduced in version 1.9.
- Fixed a resource leak related to ``MongoSourceTask.start`` that was introduced in version 1.9.

.. _kafka-connector-whats-new-1.10:

Expand All @@ -80,7 +102,7 @@ What's New in 1.10

- Added the connector name to JMX monitoring metrics.
- Added support for SSL by creating the following configuration options:

- ``connection.ssl.truststore``
- ``connection.ssl.truststorePassword``
- ``connection.ssl.keystore``
Expand All @@ -105,7 +127,7 @@ What's New in 1.9
start a Change Stream at a specific timestamp by setting the new
``startup.mode.timestamp.start.at.operation.time`` property.
- Deprecated the ``copy.existing`` property and all ``copy.existing.*``
properties. You should use ``startup.mode=copy_existing`` and
properties. Use the ``startup.mode=copy_existing`` and the
``startup.mode.copy.existing.*`` properties to configure the copy existing
feature.
- Introduced the ``change.stream.full.document.before.change`` setting that
Expand Down Expand Up @@ -136,7 +158,7 @@ What's New in 1.8
- Added several logger events and details in source and sink connectors
to help with debugging. For a complete list
of updates, see the
`KAFKA-302 <https://jira.mongodb.org/browse/KAFKA-302>`__ issue in JIRA.
`KAFKA-302 <https://jira.mongodb.org/browse/KAFKA-302>`__ issue in JIRA.
- Added JMX monitoring support for the source and sink connectors.
To learn more about monitoring connectors, see the
:ref:`<kafka-monitoring>` page.
Expand All @@ -158,7 +180,7 @@ What's New in 1.7
Sink Connector
~~~~~~~~~~~~~~

- Added dead letter queue error reports in the event
- Added dead letter queue error reports if
:ref:`the connector experiences bulk write errors <sink-configuration-error-handling-dlq-errors>`
- Added support for unordered bulk writes with the ``bulk.write.ordered`` :ref:`configuration property <sink-configuration-message-processing>`
- Added warning when attempting to use a Change Data Capture (CDC)
Expand All @@ -183,7 +205,7 @@ Sink Connector

To learn more about connection URI options, see the
`Connection Options <{+connector_driver_url_base+}fundamentals/connection/connection-options/>`__
guide in the MongoDB Java driver documentation.
guide in the MongoDB Java driver documentation.

Source Connector
~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -427,8 +449,8 @@ Source Connector
Bug Fixes
~~~~~~~~~

- Removed failures with the ``MongoCopyDataManager`` when the source database
does not exist
- Removed exceptions reported by the ``MongoCopyDataManager`` when the source
database does not exist
- Fixed the copying the existing resumability error in the Source Connector

.. _kafka-connector-whats-new-1.1:
Expand Down