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-42593) Add info about necessity of ns field. #166

Merged
merged 3 commits into from
Aug 16, 2024
Merged

(DOCSP-42593) Add info about necessity of ns field. #166

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3eb7193
(DOCSP-42593) Add info about necessity of ns field.
lmkerbey-mdb Aug 16, 2024
8239850
Empty commit.
lmkerbey-mdb Aug 16, 2024
1f47d04
(DOCSP-42593) Typo fix.
lmkerbey-mdb Aug 16, 2024
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
10 changes: 6 additions & 4 deletions source/source-connector/usage-examples/custom-pipeline.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,12 @@ to your ``pipeline`` setting:

.. important::

Make sure that the results of the pipeline contain the top-level ``_id``
field of the ``payload`` object, which MongoDB uses as the value of the
:manual:`resume token </changeStreams/#resume-a-change-stream>`.

Make sure that the results of the pipeline contain the top-level
``_id`` and ``ns`` fields of the ``payload`` object. MongoDB uses
``id`` as the value of the :manual:`resume token
</changeStreams/#resume-a-change-stream>`, and ``ns`` to generate the
Kafka output topic name.

When the application inserts the sample document, your configured
connector publishes the following record to your Kafka topic:

Expand Down
Loading