web

You’re offline. This is a read only version of the page.

Microsoft Azure | Share your Ideas

Community

Loading...

This forum

Home
Azure Cosmos DB

Azure Cosmos DB

540 Ideas

Most votes



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.

Company Response

This feature is now generally available. Can start here to learn more, https://docs.microsoft.com/azure/cosmos-db/partial-document-update 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.

Company Response

We are going to move this back to Planned until we release support for all database API's. Will then mark as completed. Thank you.

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.

Company Response

Thank you for your valuable feedback. At this time, we do not have plans to implement this feature in Azure Cosmos DB. Your input is appreciated and will be considered for future updates.

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.

Company Response

Azure 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 is1. Store every version/change as a separate item2. 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 happen from time to time!

Resource Provider / Management

Company Response

We are moving this from planned to declined. As previously mentioned, there are some complexities involved with renaming an ARM resource where the name itself is in the resource path. We are going to continue to explore options for how to enable this with the ARM team. During that time we feel it is better to reflect it in this stage. We will update this as this progresses.

[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.

Completed

Completed

Resource Provider / Management

M

Microsoft

Company Response

This 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.

Company Response

This feature is now in public preview. You can find documentation here: Delete items by partition key value - API for NoSQL (preview)

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.

Declined

Declined

Gremlin API

M

Microsoft

Company Response

This is currently not on our road map. However, we will review this item in the future as we prioritize future releases.

Support ORDER BY on the ST_DISTANCE spatial function

Ordering results by the ST_DISTANCE spatial function is currently not supported.

Company Response

This 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.

Add support for single entity retrieval instead of IEnumarable

Single \ First and so are currently not supported in Document DBFor 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 codeAdditional information: Query expression is invalid, expression return type Entities.Models.Hierarchy is unsupported. Query must evaluate to IEnumerable

SDK / Drivers / Connectors

Company Response

Thank 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 for your suggestion and everyone�s feedback.

Filters

Categories



(Select all)



All ideas



Azure Synapse Link



Backup



Billing

Stages



(Select all)



Archived



Completed



Declined



In Review

Quick links

Powered by Dynamics 365 Customer Service. Learn more here.

Privacy Terms of use

© Microsoft 2021