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?

mongodb connector 1.9.5-final

What is the connector configuration?

{
         "name": "mongodb-jsondb-connector",
         "config":
         

{                  "connector.class": "io.debezium.connector.mongodb.MongoDbConnector",                  "mongodb.hosts": "xxxxx.mongo.cosmos.azure.com:10255",                  "mongodb.name": "Cosmosdb",                  "mongodb.user": "xxxxx",                  "mongodb.members.auto.discover": "true",                  "mongodb.password":"xxxxxx",                  "database.include.list":"DataPoCDB",                  "collection.include.list":"Collection1",                  "snapshot.mode":"initial",                  "tasks.max":"10",                  "mongodb.ssl.enabled":"true",                  "capture.mode":"change_streams",                  "mongodb.ssl.invalid.hostname.allowed":"true",                  "database.history.kafka.bootstrap.servers": "xxxxx",                  "database.history.security.protocol": "SASL_SSL",                  "database.history.sasl.mechanism": "PLAIN",                  "database.history.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username= \"$ConnectionString\" password= \"Endpoint=sb://xxxx.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxxx",                  "database.history.producer.bootstrap.servers": "xxxx.servicebus.windows.net:9093",                  "database.history.producer.security.protocol": "SASL_SSL",                  "database.history.producer.sasl.mechanism": "PLAIN",                  "database.history.producer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username= \"$ConnectionString\" password= \"Endpoint=sb://xxxxx.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxxx",                  "database.history.consumer.bootstrap.servers": "xxxx.servicebus.windows.net:9093",                  "database.history.consumer.security.protocol": "SASL_SSL",                  "database.history.consumer.sasl.mechanism": "PLAIN",                  "database.history.consumer.sasl.jaas.config":"org.apache.kafka.common.security.plain.PlainLoginModule required username= \"$ConnectionString\" password= \"Endpoint=sb://xxxx.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=xxxx",                  "database.history.kafka.topic": "dbhistory.cosmosdb"          }

 }

What is the captured database version and mode of depoyment?

Azure Cosmos DB

What behaviour do you expect?

<Your answer>

What behaviour do you see?

The connector throws the below error:

Caused by: com.mongodb.MongoCommandException: Command failed with error 2 (BadValue): 'Expected type string but found int.' on server fql-env-sit-mongodb.mongo.cosmos.azure.com:10255. The full response is {"ok": 0.0, "errmsg": "Expected type string but found int.", "code": 2, "codeName": "BadValue"}
    

How to reproduce the issue using our tutorial deployment?

Connect to Azure Cosmos DB using the mandatory parameters set in the connector configuration

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>