Mongo API Support

[RobertSzkutak]

## Problem Statement
The README recommends using the MongoDB connector for the Cosmos DB Mongo API, however, it seems that since the Cosmos DB Mongo API doesn't support the connectionStatus command, newer versions of the MongoDB Connector are incompatible with Cosmos DB. Mongo rejected a PR last year to add an option that would keep Cosmos DB supported: https://jira.mongodb.org/browse/KAFKA-332

I work for Confluent and have a customer using the Mongo API variant of Cosmos DB. I'm wondering if you can share any insight into what you would recommend and how we could best support this customer? Is MSFT looking to close this gap long term by adding Mongo API support for either the connectionStatus command or by creating a 1st party connector?

## Proposed Solution
Ideally, MSFT would provide a supported solution for Cosmos DB Mongo API users to integrate with Kafka.

## Alternative Solutions
The customer could use an older version of the MongoDB connector or patch the connector but maintaining this could be increasingly challenging long term.

## Additional context
Happy to collaborate here.

Next Steps

• Team consensus to proceed
• Schedule Design Session
• Complete Design Review

[kausik96]

We are also facing the same issue. Can Somebody from @microsoft @msft please reply here ?

[kushagraThapar]

@TheovanKraay can you please help here?

[TheovanKraay]

There is no plan to support connectionStatus in Mongo RU API, and no plans to support a forked version of the connector currently. So, customers would need to use an older version of the MongoDB connector or patch as mentioned above. We do, however, plan to support connectionStatus in Cosmos DB Mongo vCore API some time in first half of 2025.

[kausik96]

Thanks for your reply ! Does this mean CosmosDB RU mode will have the same feature at all ?
And when you guys have any ETA planned for GA of the same feature please share the same here.
Thanks,
Kausik.