Azure Cosmos DB
Azure Cosmos DB is a globally distributed database service designed to enable you to elastically and independently scale throughput and storage across any number of geographical regions with comprehensive SLAs. You can develop document, key/value, or graph databases with Cosmos DB using a series of popular APIs and programming models.
Core API:
With the Core API, Azure Cosmos DB provides rich and familiar SQL query capabilities with consistent low latencies over schema-less JSON data. In this article, we provide an overview of the Azure Cosmos DB’s Core API, and how to best use the API.
Graph API:
Azure Cosmos DB provides the Gremlin graph API for graph modeling and traversal, along with turn-key global distribution, elastic scaling of storage and throughput, and low latency.
Apache Cassandra API
Azure Cosmos DB supports the Cassandra API. This means that by using existing drivers, your application written for Apache Cassandra can now communicate with Azure Cosmos DB instead of Apache Cassandra/Datastax Enterprise databases, and gain benefits like global distribution and elastic scale.
MongoDB:
Azure Cosmos DB supports the MongoDB API. This means that by using existing drivers, your application written for MongoDB can now communicate with Cosmos DB instead of MongoDB databases, and gain benefits like global distribution & elastic scale.
Table API:
Azure Cosmos DB provides the Table API for key-value workloads. This provides a premium experience for Azure Table storage with secondary indexes, global distribution, low latency, and dedicated throughput.
-
[DocumentDB] Allow Paging (skip/take)
Allowing paging would be huge. Btw, Thank You for rolling out this feature at all! It looks wonderful! Can't wait to try it! However, I won't be able to use it for actual work projects until it supports paging and sorting.
2,804 votesWe are working on some foundational pieces which will light up skip/take in future.
-
Be able to do partial updates on document
Allow to push only values for some fields of a document and not need to read the whole document and save it to documentDB.
2,495 votesWe are actively working on this feature.
-
Add Group By support for Aggregate Functions
We're really happy about the new aggregate functions that recently were announced. But without Group By support they fall short and will leave many disappointed. Please add Group By support as well.
1,876 votesStill in works, meanwhile, we recommend using the Spark connector: docs.microsoft.com/en-us/azure/cosmos-db/sp.. or docs.microsoft.com/en-us/azure/cosmos-db/ch.. to perform aggregates like Group By.
or Use Azure Stream Analytics (ASA).
-
Provide support for DISTINCT
Need to provide support for SELECT DISTINCT xyz FROM c.
1,536 votesActively working on it. Soon will update this thread with dates.
-
Batch Operation Support
Document DB should support batch operations in REST API and SDK level. It would be very useful to insert 1000 entities in one transaction.
1,198 votesPlease note it is possible to implement rich programming logic like batch import/batch delete/etc. using stored procedures. See https://github.com/arramac/azure-documentdb-dotnet/blob/master/samples/code-samples/ServerSideScripts/JS/BulkImport.js for an example of bulk import.
For use cases that need only CRUD and batch operations, the Table API for Azure Cosmos DB might be a good alternative (and supports a native batch REST API): https://docs.microsoft.com/en-us/azure/cosmos-db/tutorial-develop-table-dotnet
We are also investigating supporting a native bulk import method for all APIs (Documents, Tables, and Graph).
-
Transaction support in client SDKs
it would be useful if documentdb transactions are supported in .net, rather than just storedprocs and triggers.
using trans = newtrans()
try
db.addsomething()
db.save() //ok
db.addother()
db.save() //fail
catch
trans.rollback
end try
end using1,010 votesThanks for the feedback.
We will add this to our backlog.
Please let the feedback keep coming. We are listening!
-
Support cross-document joins
I have a many-to-many scenario that requires something like document-to-document joins.
In my app, users can "like" posts. That's three "tables" or entity sets. One each for users, likes and posts. I can't put the likes inside of either the users or the posts entities as sub-documents because there could be thousands of them. Even with 256KB documents I'd run out of room pretty quickly. I need a way to quickly get the top 100 posts that a user liked (and continue to paginate from there). I also need to go the other way. I need to get all the…
1,000 votesFor applications that require cross document join, please consider the Gremlin API: https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-dotnet, which has primitives for joins, traversals, and other graph operations.
We are evaluating expanding the SQL grammar to support graph functionality, which will provide the ability to perform cross-document JOINs. Please upvote this item to help us prioritize this work.
-
Offline version for mobile devices
Like cloudant and couchbase. To be able to have local storage which can sync with the cloud once we get a network conneciton.
It should be connection agnostic, use in the same manner if connected or not.924 votesThanks for the feedback.
This is not in our current backlog. However, we are constantly evolving and adding more features.
Please let the feedback keep coming. We are listening!
-
Allow Database Level Pricing
I am looking to convert an application from MongoDB to DocumentDB as I would prefer a managed solution but the collection pricing is absurd. The current model has 1 or 2 collections with 10+ GB of data that will grow at high rates but there are another 30 collections or more with most of them having only 10-20 records. Paying a minimum of $25 per collection is out of the question especially for dev workloads. The pricing model would change your development behaviour to just stuff everything in the same collection but then you loose a lot of the ability…
802 votes -
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)
767 votes -
Set based operations (INSERT, UPDATE, DELETE)
It would be nice to be able to update parts of documents, delete documents, and insert documents using set based operations, similar to SQL.
e.g.
UPDATE Users SET IsActive = 0 WHERE LastLogin < '2010-01-01'
DELETE FROM Users WHERE LastLogin < '2009-01-01'
INSERT INTO table2 SELECT * FROM table1746 votesWhile this suggestion is still under review at this time. In the interim, we would suggest using stored procedures for write operations as this allows you to perform write operations that span multiple documents to get transaction semantics.
Thanks,
Denny Lee
Azure DocumentDB -
Support Document Versioning
The ability to generate links to a previous version of a document would be a powerful addition DocumentDB that has many use cases.
In my case I need a self managed profile document that needs to be referenced at point in time to be tied to an event.
652 votesAzure Cosmos DB now provides the ability to access the change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed). A common pattern to implement eventing patterns is
1. Store every version/change as a separate item
2. Read the change feed to merge/consolidate changes and trigger appropriate actions downstream.You can also expire old versions using TTL: https://docs.microsoft.com/en-us/azure/cosmos-db/time-to-live
-
Add DocumentDB Emulator support for Mac OS X and *nix
The DocumentDB Emulator currently only supports Windows 10.
It would be great if support for Mac OS X could be added or documentation to run it on other platforms.
620 votesThanks for this important feedback. At present this is further out in our planning cycle, but your votes and scenarios help us prioritize it.
-
Implement LIKE keyword
Add support for the LIKE '%%' SQL keyword and associated functionality.
617 votesAzure Cosmos DB supports the CONTAINS, STARTSWITH, and ENDSWITH built-in functions which are equivalent to LIKE.
We are planning to add support for LIKE since this is a top requested item, but meanwhile, please use the other equivalent keywords.
-
Autoscale Throughput (UR/s)
Depending on the average amount of incomming requests/ required RU's, (or other parameters,)
I would like to autoscale the througput(RU/s) of a collection.584 votesThank you for all the feedback for the preview of RU/m. We are currently reviewing feedback to drive further improvements. Please stay tuned. For any questions, please reach out to us at AskCosmosDB@microsoft.com
-
Manage Azure DocumentDB using PowerShell
We need a PowerShell module for managing Azure DocumentDB
578 votesPlease see our documentation for how to manage Azure Cosmos DB accounts using PowerShell:
https://docs.microsoft.com/en-us/azure/cosmos-db/powershell-samplesLeaving this item open as it doesn’t cover all scenarios listed in the comments section.
-
I want atomic counter
I want a counter is a valid atomic in the collection. Such as use with automatic sequential number.
546 votesThe RID system property is an automatic sequential number (within a partition) encoded as a base64 string. We are planning to introduce SQL built-in functions that let you convert it to a number (and back).
-
Positional array update via '$' query support
I have posted a question in stackoverflow (https://stackoverflow.com/questions/45057385/azure-cosmosdb-mongodb-update-fields-of-an-specific-element-of-an-object-in-an) related to this issue.
518 votes -
Add "elastic pool"
Today at BUILD we saw Azure SQL DB announce elastic pools. This is awesome and what I hoped capacity units would be.
This is definitely needed if we're going to build SaaS apps with DocumentDB
1) assign collections to a pool of resources and have resources allocated dynamically to collections as needed based on demand. Hot collections just get more, idle collections get less
2) elastic query to easily write one query against all collections in a pool
3) jobs to be able to manage sprocs etc. across collections easily
496 votes -
Add support for single entity retrieval instead of IEnumarable
Single \ First and so are currently not supported in Document DB
For example, the following code:
return _client.CreateDocumentQuery<TEntity>(_collection.SelfLink).SingleOrDefault(x => x.Id == id);
causes the error:
An exception of type 'Microsoft.Azure.Documents.Linq.DocumentQueryException' occurred in Microsoft.Azure.Documents.Client.dll but was not handled in user code
Additional information: Query expression is invalid, expression return type Entities.Models.Hierarchy is unsupported. Query must evaluate to IEnumerable.
444 votesPlease not that since this item was created, we added support for Take() in the LINQ provider. So you can change the query to use Take(1).AsEnumerable().SingleOrDefault().
We are planning to extend the LINQ provider to support SingleOrDefault and other operators. This requires some additional SQL grammar support in the Azure Cosmos DB grammar.
- Don't see your idea?