Currently the query "SELECT TOP 1 * FROM C" seems to touch on all documents resulting in a huge RU usage. If no ORDER BY clause is specified this should not be necessary.

Currently the emulator installer is hard-coded to install on the C: drive, it'd be great if there was an option to install to a different drive

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.

Server-side stored procedures in Azure Cosmos DB does not support features in ES2016, such as async operators, or spread syntax. These features would make manipulating objects a lot easier, and the code cleaner.

Document databases are well suited to replication/synchronization. A Desktop/Device version of ComosDB that could be redistributed with an application would allow data to easily be synchronized between devices that go offline and the cloud.

Provide ability to encrypt data at rest using provided keys using Key Vault. This is a frequent requirement for storing anything related to the business, especially finances.

Keys will be managed by customer in that case.

Currently GeoSpatial queries are very expensive in terms of RUs compared to other non geospatial queries. It would be nice to be able to run these queries without breaking the bank!

Instead of, or in addition to, the existing ChangeFeed please publish changes to Event Grid.

This shud be mngt ops like DB create, collection create etc.
AND changes to documents, including deletes.

log @cosmosdb RU usage per query in @AppInsights (without using custom data), by configuration.

turn a key, in configuration, and have request response info, like RU charge, emitted to AppInsights.

Currently Java SDK client does not support Direct.TCP mode connection which is supported by C#.Net SDK client. Direct.TCP mode connection would have better performance compare to Direct.HTTP mode

It would be great if you could get a change feed for a very specific partition, this would eliminate the need having a global listener and having to react/route to every document through the feed instead of listening for only the particular set it cares about.

Would be great to have the ODBC driver for linux variants. We were looking to port a MongoDB application and require some sort of aggregation features on some linux machines.

In App Service Plan it is possible to configure auto scaling. I would like the same capability in CosmosDB. I.e. I could set a lower and upper RU/s and if throttling was about to occur, Cosmos DB could instead increase RU/s until the upper limit was reached or throughput was met. And Cosmos would also automatically lower RU/s if traffic is low.

i want store asp.net session state in azure documentdb.
I remember there was a special store provider for appfabric cache to store session state (configured in web.config), it's also possible with sql server. however, in documrntdb you can't do this, if i use documrntdb as my main db and im using an adhoc loadbalancer it will be great to store the asp.net session state in documrntdb.

Hello all,

As far as I see, it is not possible to throw a custom error (with a custom, user defined, error code), inside a DocDb stored procedure?

Ideally, I want to throw exceptions, in order to indicate if there is a functional error that needs to be handled by the calling client.

Now, I am throwing an Error, like this : throw new Error("[901] - Status was invalid."); and I'm checking client side to see if the error message starts with that code or not.

It would be nice if the emulator displayed some basic metrics such as RU/s or RU/m even if they were exported to a log file. This would allow us to do some "real world" analysis for better capacity planning.

For some advanced scenarios and for performance reasons, support filters (queries) on the Change Feed

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)

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