-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
1.9.0.Beta1
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
1.9.0
What is the connector configuration?
connector.class=io.debezium.connector.mongodb.MongoDbConnector
transforms.unwrap.delete.handling.mode=none
collection.include.list=****
transforms.extractKey.field=id
mongodb.password=****
tasks.max=3
mongodb.user=****
capture.mode=change_streams_update_full
transforms=unwrap,extractKey
mongodb.name=mongo-search
transforms.extractKey.type=org.apache.kafka.connect.transforms.ExtractField$Key
mongodb.ssl.enabled=true
topic.prefix=mongo-search
mongodb.members.auto.discover=true
transforms.unwrap.drop.tombstones=false
transforms.unwrap.type=io.debezium.connector.mongodb.transforms.ExtractNewDocumentState
mongodb.hosts=****
database.include.list=duom-prod
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
mongo 6.0.5
AWS / N. Virginia (us-east-1)
Sharded Cluster - 3 shards
What behaviour do you expect?
Help me with the <debezium-connector-mongodb> usage exception
What behaviour do you see?
the following exception occurred
get data from mongo:
[{
"_id":
,
"id": "kcustomer_invite_register_20230317125445409285671679057685426",
"activity_status": "SUCCESS",
"adjust_status": "",
"aliyun_risk_status": "",
"appsflyer_status": "",
"body": "{\"body\":{\"targetId\":\"2023031712544540928567\",\"targetUid\":\"2023031712544540928567\"}}",
"created": {
"$date":
},
"customer_id": "2023030309205860600005",
"google_analytics_status": "",
"modified": {
"$date":
},
"name": "invite_register",
"sls_status": "",
"source": "kcustomer",
"time":
,
"uid": "20230317125445409285671679057685426"
}]
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
How to reproduce the issue using our tutorial deployment?
Look at this code
Class: ExtractNewDocumentState.java
Code: value doesn't seem to support characters
BsonDocument keyDocument1 = BsonDocument.parse("{ \"id\" : " + keyRecord.key().toString() + "}");
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
<Your answer>
- impacts account
-
DBZ-3605 Add support for XML_TYPE column type to Debezium connector for Oracle (LogMiner)
- Closed