Azure Cosmos DB
Have feedback for Azure Cosmos DB product? Submit your idea here or upvote other ideas. All feedback is monitored and reviewed by the Azure Cosmos DB team.
This site is for feature suggestions only. For technical questions or issues, please submit them to StackOverflow,where we and the community can better help you.
Please use the following categories when submitting your idea.
Gremlin API: Graph features and capabilities using Gremlin API.
MongoDB API: Features and capabilities using MongoDB API.
Table API: Features and capabilities using Table API.
Etcd API: Features related to using etcd as a configuration store for Kubernetes.
Built-in Apache Spark: Features related to built-in Apache Spark in Azure Cosmos DB.
Built-in Notebooks: Features related to built-in Notebooks in Azure Cosmos DB.
SDK: Features related to Azure Cosmos DB SDKs for SQL API.
Change Feed: Features related to Change Feed.
Management: All management features, backup/restore,monitoring, ARM, PowerShell and CLI.
Portal: All features for Azure Portal and Cosmos DB Explorer.
Emulator: Features related to the Azure Cosmos Emulator.
Other: Features not related to any other category.
-
Support for transactions via Mongo 4.0 API
Mongo 4.0 incl transactions has been released: https://www.mongodb.com/transactions.
CosmosDB should support Mongo 4.0 API (including transactions)265 votesThis is currently not our our roadmap. Will mark this as unplanned and leave this open as we will revisit this in future planning cycles.
Thank you for your suggestion.
-
Better handling of "request limit too large"
Here (https://docs.microsoft.com/en-us/azure/cosmos-db/performance-tips) you can see that when you have exceeded your RU/s quota, Cosmos DB will respond with HTTP Status 429 with an HTTP header x-ms-retry-after-ms telling you when you can make the next request. It also says that the request will be retried automatically, if you use the SQL API.
For the MongoDB API, requests will not be retried automatically and there is nothing telling the user how long to wait before retrying. Instead you have to catch a MongoCommandException, look at the Code property for 16500 and guess when to retry,
I'd like the same support…
222 votesWe are looking at this but it is not in our immediate roadmap. Will update on whether we add this to our roadmap.
Thank you for your suggestion.
-
Support documents up to 16mb
It's not possible to migrate documents greater than 2mb, please consider increase document size up to 16mb
119 votesThanks for feedback.
We are continuously improving and adding new features, however, this is not in our priority list at the moment.
Appreciate you taking time to give us the feedback.
-
Add support for "Search text" ($text Operator)
Support for "Mongo Search Text" (https://docs.mongodb.com/manual/text-search/). Example of use:
db.stores.find( { $text: { $search: "java coffee shop" } } )
89 votesFor this we recommend using Azure Search. This is not on our roadmap. If that ever changes we will reopen this item.
Thanks.
-
Support $GraphLookup
$graphLookup is not implemented in Mongo API
If you try to do this with Mongo API (or Cosmos DB) + Gremlin you need to know what the relationships are upfront. Need DYNAMIC joins
which MongoDB supports today.47 votesThis is not on our current road map for the current calendar year. Will continue to monitor customer feedback on this.
Thank you for your suggestion.
-
Need way to create collections via the Mongo DB API with a specified RU throughput
Developers using the MongoDB API should be able to programmatically create collections of a given RU throughput, similar to the capability that the DocumentDB API already provides.
4 votesThe MongoDB API has no extensions that allow for this capability. The recommended method is to use the SQL API for .NET. Read more here, https://docs.microsoft.com/en-us/azure/cosmos-db/set-throughput#throughput-faq
-
Cosmos support of Mongo API
Currently, in Azure, we have Logic Apps, and in Cosmos, there are stored procedures, and many other features to which I am unaware. If you are using an SQL API, then you can utilize the power of Logic Apps and Stored Procedures, but if you using the Mongo API, then all of these features are lost, and your only choice is to use lambdas.
Support of the Mongo API would be fantastic. Think of the power of being to Mongo, but so much more. For example, Mongo does not support Stored Procedures. But imagine if I used Cosmos, and I…
3 votesThis is not on our road map. Will update status if that changes.
Thank you for your suggestion.
-
Support View objects similar to MongoDB
Create the capability to create views similar to MongoDB database. Views are very useful when is required to do aggregation operations, lookups in different tables as well.
2 votesThis is not on our road map and is a low priority for us unless sufficient interest and votes from users.
Thanks for your suggestion.
- Don't see your idea?