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.
-
[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.
693 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.
-
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…
642 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.
-
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 extra222 votesWork for this feature is now being planned. Will update when work on this feature starts and when it becomes generally available.
Thank you.
-
Set Account Level throughput on Cosmos DB Table API with ARM template
Make it possible to set "Account level throughput" on a Table API account through ARM template or Powershell.
According to the official Twitter handle of Azure Cosmos DB, it is only possible to set the "Account level throughput" on a Table API database account through the Azure Portal. You cannot do this with an ARM template.
https://twitter.com/AzureCosmosDB/status/117507143322931200167 votesHello.
We have reviewed this item and will look to implement before end of year 2020.
Will update here as this progresses.
Thank you.
-
Faster resource deletion
CosmosDB resources take a very long time to delete. Make this faster please!
16 votesWe have reviewed this and have added to to our committed work items for this semester.
One thing to point out however is that resource deletion for Cosmos will never be super fast. The reason is that we need to ensure that all connections and caches are drained before we delete the resource. This can some minutes for this to happen.
We will update here when we release this work.
Thank you.
-
We need to view the last backup date & time and a flag to indicate if it has been backed up successfully.
We need to view the last backup date & time and a flag to indicate if it has been backed up successfully. This is for resource governance and data availability purposes. Management needs to view governance dashboards and verify backups are successfully completing as described in the documentation.
15 votesThis is currently planned with point in time restore feature we are currently working on. When this is released as GA customers will have full control via Azure Portal.
Thanks.
-
Make autoscale work like other services' autoscale and pricing
Autopilot in general cost 50% more per 100 RU than the dedicated throughput and is cost effective if there is significant variation from peek load usage. This is confusing as customer that auto pilot could be costing more in some sceanrio like if you only lower loads on weekends etc. And morever this is different from all the other services available in Azure where the Auto Scale Up/down does not have a different pricing then the regular mode. this cost should not vary with provisioned throughput ...
11 votesUpdate. We will move this to unplanned as we may revisit this and offer an autoscale similar to what is described.
Will change the title to better reflect the ask however.
-
2 votes
Work on this has started. Will update when complete.
Thanks.
- Don't see your idea?