-
Notifications
You must be signed in to change notification settings - Fork 21.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermixing the Cosmos DB: MongoDB API with the Cosmos DB: DocumentDB API #5460
Comments
Edit: |
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate. |
@MicrosoftDocs/azure-cxp-triage - Please add the functions label to this. |
@llauner you are right that at this time, the Azure Cosmos DB trigger, input bindings, and output bindings work with SQL API and Graph API accounts only. If you want to propose that Functions add support for MongoDB API, please provide that feedback here. In the meantime, if you want to use MongoDB APIs in a function, you can still use the Mongo Client from inside your function, just not with the trigger/bindings. |
I don't believe this is an Azure functions limitation, but rather a Cosmos Change Feed limitation, which also does not support the MongoDB API atm. I've started a User Voice on this here: https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/33626986-add-change-feed-support-to-mongodb-api |
@llauner Thank you for the feedback! I believe this issue is resolved from a documentation perspective. #please-close |
Now Change Feed Cosmos Mongo API is supported, looks like the Azure Functions for Cosmos Mongo Trigger is still not working, if working, please share any references documents or samples (Java Preferred) for the same. |
I'm experiencing this exact behaviour:
https://social.msdn.microsoft.com/Forums/en-US/e0ffdbcd-0b43-4cd5-9d21-1a95ce0279dd/mongodb-contains-v-and-t-in-query-result?forum=azurecosmosdb
Is there a way to update the trigger so that it returns a standard mongoDB json as opposed to the json containing $t and $v ?
The DocumentDB API is not available anymore in CosmosDB, so how come the trigger is still using it ?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: