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 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.
5,704 votesHello. We currently have a private preview for Partial record updates (aka Patch) available for sign-up.
If you are interested in signing up for this private preview program, please visit, https://aka.ms/cosmosdbpatch
Thank you.
-
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,617 votesWe’re going to move this back to Started until we release support for all database API’s. Will then mark as completed.
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,247 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 table11,025 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 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.
1,024 votesHello. Our apologies for the delay in an update here.
We are actively working on this and have a new ETA of Q2 2021.
Thanks for your patience.
-
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.
814 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 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…
738 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.
-
[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.
730 votesThis feature is now available in Preview.
You can read more here.
https://docs.microsoft.com/en-us/azure/cosmos-db/continuous-backup-restore-introductionThanks.
-
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.
698 votesWe’re looking to get some feedback on this feature and would love for you to try out a preview.
Sign-up: https://aka.ms/cosmosPkDeleteSignup
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.
654 votesThis is currently not on our road map. However, we will review this item in the future as we prioritize future releases.
-
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.
517 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 ORDER BY on the ST_DISTANCE spatial function
Ordering results by the ST_DISTANCE spatial function is currently not supported.
504 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.
-
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.
476 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.
-
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.
370 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.
-
Support documents up to 16mb
It's not possible to migrate documents greater than 2mb, please consider increase document size up to 16mb
327 votesThank you for the feedback! We have begun development for supporting larger documents sizes.
We will be hosting a preview in the coming months and would love to get your support in testing and feedback.
Please sign up here if you are interested in participating in the upcoming preview: https://aka.ms/cosmosdb-big-item-size-preview
-
Support filters (queries) on the Change Feed
For some advanced scenarios and for performance reasons, support filters (queries) on the Change Feed
322 votesThis feature is now planned for this current semester ending in June.
Will update as work progresses.
Thank you.
-
Improve scaling down experience: remove redundant physical partitions
During initial import we increased RU to 200K. Cosmos Db SQL API created 20 physical partitions with 10K throughput each.
During regular day we just need 30K Ru. That would mean each physical partition would have only 1,5K RU allocated and a lot of redundant partitions with possible expensive cross-partition calls (total data size is less than 30GB)Is there way to decrease amount of physical partitions to reasonable value?
In a nutshell it is not fair pricing, when you are limited to 1,5K RU and a lot of cross-partition calls you have to pay extra306 votesWork for this feature is now being planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
CouchDB API for Cosmos DB
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.
275 votesUnmerging this with Offline mobile device support. Modifying title as it appears this ask is to have Couch DB add to our multi-model API support. No change in status.
-
Support case insensitive indexing
Order by returns lowercase characters before uppercase characters.
x
y
z
A
B
CI know you can work around this by storing an all lower or all upper case version of the string you want to query by on your object but over time and scale that does add to your RU usage
239 votesThank you for your feedback! We are planning on additional work here to make it possible to do case insensitive sorting.
Thanks.
-
Execute a procedure when TTL expires
I would like to execute a procedure when TTL expires. For example, when TTL expires I would like to also delete some related records from Azure table storage.
216 votesWhen we support change feed deletes, we will also indicate whether the delete is due to TTL. This will allow developers to write custom code that is executed each time data is deleted (for example, after they’ve processed that change).
- Don't see your idea?