Release v17.24.5
Summary
The MongoDB in Azure CosmosDB behaves differently than an official MongoDB instance when it comes to querying collections that does not exist. While an official MongoDB instance will return an empty cursor or null, the Azure version will return an error saying "Collection not found". This PR fixes this by mimicking the behavior of what is expected when working with MongoDB.
Fixed
- Added specific handling for
Collection not foundin the cross cuttingMongoCollectionInterceptorto make this completely transparent to any consumers.