Allow a set of keys for read-write or read-only that are restricted to the Collection level or the DB level. Enable multiple applications to have different levels of permission to a single Cosmos DB.

Support for schema definition (get all distinct property names and types in a collection)

It would be nice to have the ability to execute Gremlin queries against the Graph API from a stored procedure. Ideally, this would also enable transactions.

Azure Premium Storage does not support block blobs or append blobs. These blob types are useful when information must be written and/or read from multiple machines in a cluster.

Cosmos DB should support the block blob and append blob APIs to provide an SSD-backed, faster alternative to the Azure Blob API.

Please provide an option to connect local DocumentDB emulator with Cloud Explorer inside Visual Studio via a connection string.

It will be helpful to have features like
- directly committing the stored procedure/functions/trigger to source control from there instead of going through all copy-paste.
- creating/updating/triggering a stored procedure from source control

It would be awesome if we could load external async JavaScript libraries into Stored Procedures - async, q, or rxjs would work.

We frequently make multiple calls into DocumentDB with our sprocs and these libraries would allow us to easily use promises and control the flow without getting into curly brace ****.

I have some code on providing AUCost data. I need to write it twice for StoredProcedureResponse and ResourceResponse, because they don't implement a common interface, at least in the .NET Core SDK.

We can set/get a specific property by propertyName as a key.
So it's kind of key-value pair collection.
I need to enumerate all properties in a Document without re-serialize and deserialize as enumerable type.

I think about IEnumerable<KeyValuePair<string, object>> implementation for the Document class.
So that I can enumerate document's properties like:

for each (prop in myDocument)
{
var propertyName = prop.Key;
var propertyValue = prop.Vaule;
}

Or, I can treat it as a Dictionary so that I can control key-comparison method:

var dic = new Dictionary<string, object>(myDocument, StringComparer.OrdinalIgnoreCase);

Since Cosmos DB with the Mongo API does not support all Mongo commands, I would like to be able to configure Cosmos DB accounts to support multiple apis (e.g. Mongo and Sql/DocumentDB) as described here: https://stackoverflow.com/questions/44247726/is-there-a-way-to-configure-cosmosdb-to-use-both-the-sql-documentdb-and-mongod

Why not?, Microsoft now love the opensource too, make Cosmos DB a opensouce database

Support the Collection Default TTL to be set by the Azure Cosmos DB Rest API

Support multiple write regions natively in a single cosmos db collection. Currently to build globally distributed apps, the application need to query two separate collections and merge the results. Enable true global distribution with active - active pattern and not just global replication.

Please compress data in place for more efficient use of storage.

For example, I recently exported the entire dataset from a collection and gathered the following stats:

DocumentDB Data Storage: 627 MiB (including hidden fields and other overhead I assume, but not Indexes)
Exported JSON: 461.72 MiB
Compressed JSON: 47MiB

So potentially a 10x saving in data storage size.

It needs to be possible to create an index right out of the portal and not only via issueing code as explained here: https://docs.microsoft.com/en-us/azure/documentdb/documentdb-indexing-policies -- this could be a function you can run, similar to fuctions for relational databases.
As-is working with piles of ingested JSON data requires me to do indexing first and the portal UI could be more helpful with that. Thanks!

If partial updates are going to be supported please consider to support native array functions for documents.

Depends on:
https://feedback.azure.com/forums/263030-documentdb/suggestions/6693091-be-able-to-do-partial-updates-on-document

https://feedback.azure.com/forums/263030-documentdb/suggestions/6346033-set-based-operations-insert-update-delete

It's not possible to migrate documents greater than 2mb, please consider increase document size up to 16mb