debezium / debezium/dbz

resume token to be present in topic messages when there is any creation , deletion or update of documents in mongodb [DBZ-5851]

Open
#718 0 comments 0 reactions 0 assignees View on GitHub
component/mongodb-connector migrated-from-jira type/enhancement
Dominant language
HTML
Stars
6
Forks
8
Avg merge
2d 19h
Merged PRs (30d)
1

Description

Migrated from [DBZ-5851](https://issues.redhat.com/browse/DBZ-5851)

In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
h1. Bug report

For bug reports, provide this information, please:
h2. What Debezium connector do you use and what version?

Mongodb
h2. What is the connector configuration?

{ "name": "mongodb-connector1", "config": \{ "connector.class": "io.debezium.connector.mongodb.MongoDbConnector", "mongodb.hosts": "myreplica/localhost:2717", "topic.prefix": "mongodb", "schema.history.internal.kafka.bootstrap.servers":"localhost:9092"} }
h2. What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

h2. What behaviour do you expect?

resume token in the messages
h2. What behaviour do you see?

no resume_token
h2. Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

h2. Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide [DEBUG/TRACE|https://debezium.io/documentation/reference/stable/operations/logging.html] level log)

h2. How to reproduce the issue using our [tutorial|https://github.com/debezium/debezium-examples/tree/main/tutorial] deployment?

h1. Feature request or enhancement

For feature requests or enhancements, provide this information, please:
h2. Which use case/requirement will be addressed by the proposed feature?

h2. Implementation ideas (optional)

Contributor guide

Open the contributing guide

Research direction

Start with the MongoDbConnector configuration shown in the report and use the linked tutorial deployment to reproduce document creation, deletion, and update events. Trace the resulting topic messages and verify that each contains the expected resume token; the report does not name source files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.