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.
-
Azure CosmosDB is too expensive for small but multiple collections
Currently using on-prem MongoDB (on Linux) and wish to move to Azure, but I find CosmosDB is too expensive for small but multiple (MongoDB)collections because it seems that a minimum of 400 RRU's/per second will be charged for each collection.
The terminology used on the pricing web pages is somewhat unclear though and I am not sure if the pricing for the minimum of 400 RRU's/second applies to partitions or collection (or if these terms are in fact identical semantically)
1,565 votesCosmos DB supports sharing throughput across multiple collections with database-level throughput. This costs approximately $24/month.
Thank you for your feedback on this item. Will be closing this item at this time.
Thank you.
-
Easily start/stop DocumentDB service
Should be away to "turn off" DocumentDB service or at least shutdown a database instance.
Right now the only way I know is to delete the DocumenbtDB service :(
459 votesThanks for the feedback. Cosmos DB is a stateful service that requires system resources set aside to preserve state.
-
LinqPad driver for DocumentDB
LinqPad is insanely useful for testing Linq based queries. it is also much quicker doing it here than in VS.
333 votesClosing as this has been resolved per comment below.
Thanks.
-
Native support for sub-query projections
Support for sub-query projections like,
SELECT food.id,
food.description,
food.tags,
(SELECT food.servings.description FROM food.servings) AS SimpleServings
FROM food59 votesWe support this today. Read here for more information and examples. https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-sql-query#SelectClause
Thanks.
-
Permit executing a stored procedure from another stored procedure
function () {
var context = getContext();
var collection = context.getCollection();collection.executeStoredProcedure('foo', {}, function (error, result){});
}
49 votesClosing item due to lack of feedback.
Overall this is not something we foresee implementing for a couple of reasons. But mostly, it would require the use of locks on data which we would not do as it could impact latency SLAs.
-
Support Querying a Subset of Logical Partitions in a Partitioned Collection
With the 10GB limit for a logical partition, there is a possibility where a partition key cannot be broken down far enough to avoid the upper limit without implementing a partitioning scheme similar to:
Partition Keys:
{Tenant Id}{Document Type}{Partition 1}
{Tenant Id}{Document Type}{Partition 2}
{Tenant Id}{Document Type}{Partition 3}
.
.
.
{Tenant Id}{Document Type}{Partition N}Where N is a defined as the total # of partitions per tenant id / document type combination to have. This is just an example where a single collection contains data from multiple tenants and document types, but could apply to other scenarios as well.
…
38 votesHello and thank you for your suggestion.
The ability to limit the partitions included in a query can be achieved by simply including the partition key range within the where clause using IN and not using the feedoptions to pass the partition key value.
If you have additional questions on this, please feel free to email us askcosmosdb@microsoft.com
Thank you.
-
Better documentation on integration with Logic Apps (or bugfix?) - We have serious difficulties with an error on "PartitionKey"
We are trying to do serverless with logic apps and have connected the Logic App to an Event Grid Topic. Our intent is to store events in Document DB, but we are unable to get it to work because of errors regarding the Partition Key. We have tried all possible strings in the partition key field and created a number for collections with different partion keys. We don't know what black magic spells we need to use and cannot really find good documentation with examples of such operations on the docs for either Cosmos DB or Logic Apps.:
One of…
33 votesClosing. If you still require assistance, please email us at askcosmosdb@microsoft.com with more details and we will resolve your issue.
Thank you.
-
Allow nested properties with Resource.SetPropertyValue(string,string)
For a given document:
{
"id": "CDC101",
"title": "Fundamentals of database design",
"authordetails": {
"Name" : "Dave",
"Age : "33"
},
"credits": 10
}It would be useful to be able to call:
doc.SetPropertyValue("authordetails.Name", "Mike");
23 votesWe are currently working on big improvements on .NET SDK, that will be released very soon. Once released, these property methods will become obsolete.
Thank you for your suggestion.
-
Visual studio service explorer integration
All major azure services are integrated with Visual Studio and server explorer. It could be resonable if DocumentDB will be added in a next version of sdk.
21 votesClosing as service explorer is deprecated.
Thank you.
-
Less complex pricing model
I know that you've designed the RUs to be simple but I don't think they are after all... I hope you can find a better alternative or at least some complementary flat pricing tiers.
16 votesClosing as no response to request for feedback.
-
Reduce in JavaScript Language Integrated Query API
Add Reduce function to JavaScript Language Integrated Query API
Please add __.reduce() to the JavaScript Language Integrated Query API. I'm using the other chainable functions but really need reduce.
16 votesClosing due to no response. Will change status if sufficient interest.
-
Open Source Microsoft.Azure.Graphs
Please open source the library so that the community can help contribute to the code and especially the docs. I have had to decompile the library on several occasions to figure out what I was doing wrong. Having access to the test suite is a form of documentation in itself that would be super useful for consumers of the API.
Even if you are not actively accepting PR's, having the code be source open is still a benefit to everyone.
Thanks!
16 votesMicrosoft.Azure.Graphs is now deprecated. Use Gremlin.Net.
-
Run Jepsen tests on DocumentDB
Running Jepsen tests on DocumentDB will allow users to better understand the various consistency options provided. It will also assure users that the database doesn't lose or corrupt data (for example MongoDB isn't considered very safe according to these tests)
14 votes -
Client for WinRT
A client for WinRT (Phone too?) is very important. It's makes DocumentDB "usable" from Store and Phone apps.
13 votesWith the deprecation of WinRT and phone we are closing this item.
-
Execute transient JavaScript from client
It would be very useful to be able to execute JavaScript against a collection without first having to store it.
9 votesClosing as there is no additional information on this requests.
-
Support documenting a collection
Add the ability to store some meta-documentation along with a collection. The idea being that it's very convenient to document what the collection is used for or how to interact with it. This is especially useful because you can interact with the documents directly in the Portal.
9 votesThe pattern for documenting resources deployed into Azure is to use tags. These are used extensively by customers as well as partners who build services to manage customer deployments and resources.
Thank you for your suggestion.
-
Bug: Unique keys not working for new collections in CosmosDB
Over the past week, when creating new collections with unique key constraints in an existing DB the constraints are not adhered to. Previously created collections with constraints still obey them.
Looking at the network traffic that goes out when you create a collection, there are no fields denoting the added unique key constraint. The 'colls' request to retrieve the collections also shows no unique keys for the created collection, but previously created collections have this data present.
We are using a Mongo/CosmosDB, and creating collections via the portal. We have tried this with multiple different cosmosDB instances across multiple accounts.
…
8 votesFor bug reports, please contact us at askcosmosdb@microsoft.com so we can much better assist you directly.
Thank you.
-
SELECT TOP 1 * FROM C should not result in full scan
Currently the query "SELECT TOP 1 * FROM C" seems to touch on all documents resulting in a huge RU usage. If no ORDER BY clause is specified this should not be necessary.
7 votesThanks for the feedback.
Select top 1 does not do full scan
-
Show CosmosDB Limits in Usage & Limits and API
You have a CosmosDB limit of 50, there is no way of understanding if this limit is close or reached in Azure, there is no way to query the API or see the limit in the tab Usage & Limits.
- Please add and visualize this limit so there is a possibilty to understand and prevent reaching a no deploy error.
"The subscription is exceeding the maximum number of allowed DatabaseAccounts. The current DatabaseAccount count is 50 and maximum allowed DatabaseAccounts are 50"
7 votesWe will scale to anything you need so publishing any limits does not make sense for our customers. We set the account limit to 50 because customers don’t tend to create large numbers of accounts but grow numbers of databases and containers within their accounts because they have the same consistency and replica regions.
If you have any questions about the scale Azure Cosmos DB provides, send email to askcosmosdb@microsoft.com.
Thank you.
-
Storage Explorer: Cosmos DB Graph API - Show 'Documents'
For some unknown reason I can not use the Azure Storage Explorer to list my documents of a Cosmos DB with the Graph API. When I navigate to the db, I can only see 'Stored Procedures', 'Triggers' and 'User defined functions', but not the 'Documents' which are available when I add a Cosmos DB with the Document API. Could you please enable this in the Storage Explorer?
7 votesWe took a closer look at this request. There is a workaround if you use the documents endpoint in the Azure storage explorer. This will let you see the Documents.
Will close this request as this is the recommended way to do this.
Thanks.
- Don't see your idea?