Skip to content
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

Closed
llauner opened this issue Mar 8, 2018 — with docs.microsoft.com · 7 comments
Closed

Comments

Copy link

llauner commented Mar 8, 2018

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.

Copy link
Author

llauner commented Mar 8, 2018

Edit:
The above tutorial assumes that we're using the SQL API.
This does not work with a cosmosDB configured with the MongoDB API
Any chance to have the same feature supported with mongoDB ?

@BryanTrach-MSFT
Copy link
Member

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@mimig1
Copy link
Contributor

mimig1 commented Mar 9, 2018

@MicrosoftDocs/azure-cxp-triage - Please add the functions label to this.

@ggailey777
Copy link
Contributor

@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.

Copy link

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

@SyntaxC4
Copy link
Contributor

SyntaxC4 commented Mar 15, 2018

@llauner Thank you for the feedback!
@samirageb Thank you for opening the Product feedback on user voice, it's greatly appreciated!

I believe this issue is resolved from a documentation perspective. #please-close

@sajaynambiar
Copy link

sajaynambiar commented Mar 31, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants