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.
-
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.
4,824 votesWork on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
-
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.
2,028 votesJust a quick update. Work on this feature continues but is taking longer than expected.
We have recently published guidance how how users who can run Windows in a VM whether on Parallels or Virtual Box with a Mac or Linux host can use the Cosmos emulator. Please feel free to use this as a workaround.
https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-on-mac-or-linuxWhen this feature is complete we will update here.
Thank you.
-
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,294 votesWe recently released support for client-side transactions in our .NET SDK.
https://devblogs.microsoft.com/cosmosdb/introducing-transactionalbatch-in-the-net-sdk/
We would like to get your feedback on this to understand if this meets your needs for transaction support. Please read our announcement and/or feel free to try our new support then please respond to this one question survey.
Thank you.
-
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,190 votesMoving to unplanned (Backlog).
Apologies. This status should have been changed.
This is not on our current roadmap for this semester ending in June. Will again evaluate for H2 2020.
Thank you.
-
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 table1922 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.
-
Implement LIKE keyword
Add support for the LIKE '%%' SQL keyword and associated functionality.
824 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.
-
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.
830 votesUpdate on this item.
Bytecode implementation is now targeting the first half of 2020 to provide stability and performance improvements in the platform.
Apologies for the delay. We are continuing to work on this. Will announce here when this becomes available.
Thanks.
-
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.
776 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
-
[CosmosDB] Be able to manage Backup and Restore with Portal and APIs
Please provide the ability to manage backup and restore on our own.
Restore through support is not clear and inconvenient.
It turned out restore is only available through paid support plan.
This document https://docs.microsoft.com/en-us/azure/cosmos-db/online-backup-and-restore#restoring-a-database-from-an-online-backup does not say it in any word.
The situation made our customer extremely unhappy.
616 votesWe are currently have on our road map this feature for Point-in-Time Restore (PITR) with continuous and on-demand backups. We will update the status here as this feature progresses.
Thanks.
-
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.
577 votesThis is currently not on our road map. However, we will review this item in the future as we prioritize future releases.
-
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.
540 votesWork on this item has started. Will update as this progresses.
Thank you.
-
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…
513 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 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.
502 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…
-
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.
459 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.
-
Support ORDER BY on the ST_DISTANCE spatial function
Ordering results by the ST_DISTANCE spatial function is currently not supported.
414 votesThis item was incorrectly marked as started. Actual work on this item has been deferred but is still planned.
Will update when this work is started.
Thank you.
-
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)381 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.
-
Implement a graphql provider
graphql {http://graphql.org/} is becoming increasingly adopted by front end frameworks (including mobile) for querying backend / API data.
Rather than having to translate each graphql query into a DocumentDB client call it would be optimal and very powerful to issue the query directly.
It would also provide enhanced query abilities over the existing REST approach.
332 votesApologies for the confusion on our part.
This is currently not on our roadmap. However, we will review this item in the future as we prioritize future releases.
Thanks 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…
299 votesWe now have a preview for a feature that will simplify the handling of 429, Request rate is large errors. If you are interested in participating in this preview, please email: cosmosdbmongopreview@microsoft.com.
Thank you.
-
Integrate with Azure Active Directory
Really need to be able to set resource level access control integrated with Azure Active Directory. The current built-in user / resource access control is a pain to use and we end up with just using the master key and giving everyone access to everything.
Azure SQL DB already has this, and is a pleasure to work with.
Perhaps you should take a leaf from your sister team on this -
292 votesWork on AAD Support for control plane has started. Will update here as this feature moves into generally availability.
Thank you for your suggestion and votes.
-
Support the CouchDB replication protocol
Support the CouchDB replication protocol so that we can sync with PouchDB or Couchbase Lite NoSQL databases on mobile devices for superior online / offline capabilities.
274 votesUsing Change Feed functionality (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed)
you might be able to sync with PouchDB or Couchbase Lite.
- Don't see your idea?