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.
SQL API:
With the SQL 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 SQL API, and how to best use the API.
Gremlin API:
Azure Cosmos DB provides the Gremlin API for graph modeling and traversal, along with turn-key global distribution, elastic scaling of storage and throughput, and low latency.
Cassandra API
Azure Cosmos DB supports the Cassandra API. This means that by using existing drivers, your application written for 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 API:
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.
-
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.
3,522 votesWork on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
-
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.
2,511 votesThis feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting will be notified.
Thank you for your patience.
-
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,421 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.
-
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.
1,344 votesWork on this feature has started. Will update here when this feature moves to general availability.
Thank you for your suggestion and votes.
-
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.1,320 votesFor any questions, please reach out to us at AskCosmosDB@microsoft.com
-
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,168 votesThis is currently not on our roadmap. However, we will continue to review this item in the future as we prioritize future releases.
Thank you for your suggestion and for the comments.
-
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.1,120 votesWe are currently reviewing this for future inclusion on our roadmap. Will update here on status as this progresses.
Thank you for your suggestion
-
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 table1853 votesThere are multiple responses to this suggestion.
Support for SQL-like syntax for UPDATE, DELETE and INSERT INTO are not on our road map at this time.
However, the underlying functionality for an UPDATE, SET is essentially a PATCH. This functionality we are actively working on. See this User Voice item here to track for future updates. https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/6693091-be-able-to-do-partial-updates-on-document
Thank you for your suggestion.
-
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.
723 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
-
Implement LIKE keyword
Add support for the LIKE '%%' SQL keyword and associated functionality.
708 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.
-
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.
665 votesWe are actively working on this feature. We will update this item when this feature ships so you will receive an update.
Thank you for your feedback.
-
Support Gremlin Bytecode to enable the fluent API of Gremlin.NET
Azure Cosmos DB Graph API doesn't support Gremlin Bytecode. Therefor it is not possible to use the fluent traversal API of Gremlin.NET.
Within the Azure Cosmos DB Graph .NET API (https://docs.microsoft.com/en-us/azure/cosmos-db/graph-sdk-dotnet) it is recommended to use Gremlin.NET. So it would be really nice if all features of Gremlin.NET would be supported.
See also the idea of a "better type-safe APIs fro Gremlin" (https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/19340761-better-type-safe-apis-for-gremlin) within the Graph API feedback.
559 votesWork on Bytecode support has started. Will update here when this becomes generally available.
Thank you for your suggestion and 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.
479 votesThank you for your feedback. I have discussed this in more detail with our team.
You are correct the workaround suggested to use .AsEnumerable().FirstOrDefault(). should not be a recommended work around. This way results in materializing all documents on the client first before getting the 1st document, which is not very efficient and the exact opposite of what you are trying to achieve.
Instead we recommend you use Take(1).AsEnumerable() and then .First() or .Single() or .FirstOrDefault() for Single() and First(). Take(1) is translated to SELECT TOP 1 and is processed server-side so more efficient than the previous suggestion and is what you are trying to achieve.
As to the original ask. The support for these operations can be done, but this work is not prioritized against the other work we want to deliver. I will move this back as unplanned but please note this is on our roadmap.
Thanks again…
-
Support Cypher as a query language for Graph data
Add Cyhper (see http://www.opencypher.org/) as a language to query graph databases. Cypher is a human readable query languages to easily access a graph database.
441 votesThis is currently not on our road map. However, we will review this item in the future as we prioritize future releases.
-
Add ability to rename databases and collections
It should be possible to rename databases and collections.
This feature is universal in all if not the vast majority of database products.
Lack of ability to rename anything makes it very hard for us to manage releases if we are adding new data. Currently, we have to create a copy of the existing database (which is a feat in itself, since this again is not core functionality), make the change there, and then re-point the website to the updated database. All this time, we are incurring extra costs and inconvenience.
Renaming things also allows us to correct typos, which…
329 votesThe ability to rename databases and collections is not currently something that is in our road map.
Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.
Thanks for your request and input on this. We may consider this for a future planning cycle.
thanks.
-
Add the ability to delete ALL data in a partition
In a partitioned collection, it would be useful to have the option delete all data with a given partitionId.
319 votesThis is not currently on our road map. However, we will look at this in our next feature review and will provide update on status.
Thank you.
-
Cosmos DB BulkExecutor for .NET Core
I would like Azure Cosmos DB BulkExecutor library for .NET Core compatible version.
Recent application often uses Microsoft.Azure.DocumentDB.Core package, so the need for the .NET Core version is high.
316 votesWork on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
-
Linq provider should respect JsonSerializerSettings ContractResolvers
JsonSerializerSettings are now supported when creating the client, as per https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/6422364-allow-me-to-set-jsonserializersettings
However, when using for example a CamelCasePropertyNamesContractResolver to store the data, the linq queries will fail if the properties on the POCO classes are Pascal case.
310 votesThis is currently not on our roadmap. However, we will continue to review this item in the future as we prioritize future releases.
Thank you for your suggestion.
-
OpenSource DocumentDB .NET SDK
Unlike this thread
https://feedback.azure.com/forums/263030-documentdb/suggestions/6334154-open-source-documentdbWe would like to have only the .NET SDK as opensource
https://github.com/Azure/azure-documentdb-dotnet/issues/128I have been programming against docdb with .Net for more than one year now and 80% of my problems come from the .NET SDK. We must be able to step into source code easily and propose pull requests to fix bugs. This will help Microsoft DocDB dev team to speed up corrections and features on this SDK.
306 votesThis is currently on our road map and actively being worked on now in addition to other improvements. Stay tuned for an announcement on this coming soon.
Thanks.
-
Support ORDER BY on the ST_DISTANCE spatial function
Ordering results by the ST_DISTANCE spatial function is currently not supported.
303 votesWork on this feature has started. Will update here when this becomes generally available.
Thank you for you suggestion and votes.
- Don't see your idea?