Azure Cosmos DB
Azure Cosmos DB is a globally distributed database service designed to enable you to elastically and independently scale throughput and storage across any number of geographical regions with comprehensive SLAs. You can develop document, key/value, or graph databases with Cosmos DB using a series of popular APIs and programming models.
SQL API:
With the SQL API, Azure Cosmos DB provides rich and familiar SQL query capabilities with consistent low latencies over schema-less JSON data. In this article, we provide an overview of the Azure Cosmos DB’s SQL API, and how to best use the API.
Gremlin API:
Azure Cosmos DB provides the Gremlin API for graph modeling and traversal, along with turn-key global distribution, elastic scaling of storage and throughput, and low latency.
Cassandra API
Azure Cosmos DB supports the Cassandra API. This means that by using existing drivers, your application written for Cassandra can now communicate with Azure Cosmos DB instead of Apache Cassandra/Datastax Enterprise databases, and gain benefits like global distribution and elastic scale.
MongoDB API:
Azure Cosmos DB supports the MongoDB API. This means that by using existing drivers, your application written for MongoDB can now communicate with Cosmos DB instead of MongoDB databases, and gain benefits like global distribution & elastic scale.
Table API:
Azure Cosmos DB provides the Table API for key-value workloads. This provides a premium experience for Azure Table storage with secondary indexes, global distribution, low latency, and dedicated throughput.
-
Allow multi Order By
From what I see it is impossible to run a query with more than one column in the Order By.
436 votesMulti-order work is underway. We will post an update as soon as we get closer.
-
Support ORDER BY on the ST_DISTANCE spatial function
Ordering results by the ST_DISTANCE spatial function is currently not supported.
224 votes -
Cosmos DB BulkExecutor for .NET Core
I would like Azure Cosmos DB BulkExecutor library for .NET Core compatible version.
Recent application often uses Microsoft.Azure.DocumentDB.Core package, so the need for the .NET Core version is high.
199 votes -
Support sub-query functions like EXISTS, NOT EXISTS
It would be great to query within document array's without having to join them in the root's FROM-clause.
(And likely, this also the creates the possibility to implement LINQ support for Any() and All())
example:
SELECT author
FROM author
WHERE EXISTS
(SELECT b
FROM author.Books b
WHERE b.YearOfPublishing < 1980)Although there are workarounds they all have nasty side effects:
1: In the following example the join results in non-unique results due to multiple books published before 1980 within single author-document:
SELECT author
FROM author
JOIN b IN author.Books
WHERE b.YearOfPublishing < 19802: In the following example a UDF…
179 votes -
Support LINQ ANY or WHERE for child object collections
Example trying to query Sales
var querySales = DocumentDb.Client.CreateDocumentQuery<Sale>(collectionLink)
.Where(q => q.Type == "Sale" && q.Stage <= 99 && q.InvolvedParties.Any(qq => qq.Id == userId))Buy ANY not supported
Also tried
.Where(q => q.Type == "Sale" && q.Stage <= 99 && q.InvolvedParties.Where(qq => qq.Id == advisorUserId).Count() > 0)get WHERE not supported
Really want the DB to perform the search as a lot of results will come back.
sample data:
{
"id": "af10eebf-b0b6-49d5-8db5-96f54c4985d2",
"Type": "Sale",
"GroupId": 1,
"InvolvedParties": [
{
"Id": "344595a3-4e73-4bd5-9988-849858f045f1",
"PartyType": 0,
"Name": "test user"
}
],104 votes -
Native support for sub-query projections
Support for sub-query projections like,
SELECT food.id,
food.description,
food.tags,
(SELECT food.servings.description FROM food.servings) AS SimpleServings
FROM food55 votes -
DocumentDB auto scale
Please provide auto scale option in DocumentDB for scaling down and scale up of collection based on RU running.
53 votes -
Support ordering by multiple properties
As per the DocumentDB SQL Syntax docs:
"While the query grammar supports multiple order by properties, the DocumentDB query runtime supports sorting only against a single property..."
It would be great if this limitation was removed.
Thanks!
51 votes -
.NET SDK support in UWP apps
The following message is generated if one attempts to add the Microsoft.Azure.DocumentDb nuget package to a Universal Windows Platform app:
Some packages are not compatible with UAP,Version=v10.0 (win10-x64-aot).51 votesTry this git preview package https://github.com/Azure/azure-documentdb-dotnet/blob/master/Microsoft.Azure.DocumentDB.Core.1.4.0-preview.nupkg
-
Permit executing a stored procedure from another stored procedure
function () {
var context = getContext();
var collection = context.getCollection();collection.executeStoredProcedure('foo', {}, function (error, result){});
}
45 votes -
Deploy Stored Procedures from Source Control
It would be great if we could deploy sprocs from visualstudio.com as we can with Azure Functions or Azure Web Sites.
45 votes -
stored procedures & functions in .NET (C#)
Would be great to have the option to implement stored procedures, functions and triggers in .NET (C#) as well.
43 votes -
Order By Null Handling
Currently if you do an order by on a nullable value, the documents are not returned at all. Please add functionality similiar to Application Insights where you can specify if the documents with the null value appear at the beginning or end of the sort.
40 votesWe will be addressing support for consistent ordering of different types (string, number, null). Thanks for bring this to our attention.
Thank you,
Aravind Ramachandran
Azure DocumentDB -
Support multiple collections in stored procedures
Currently CosmosDB Stored procedures only allow access to a SINGLE collection (because they seem to be scoped to collections rather than to the database), via getContext() :
var collection = getContext().getCollection();
But any "useful" / "real-life" application using ComosDB will typically have to interact with more than one collection. For example, it is currently IMPOSSIBLE to insert documents into two distinct collections within a database using a single stored procedure -- a VERY SERIOUS drawback / limitation.
I would propose that stored procedures be scoped to the database level and then we would be allowed to do something like:
var…
37 votes -
The ability to reference JavaScript libraries (e.g. underscore) within server-side scripting
It'd be nice to be able to reference javascript libraries within server-side scripting. Something like an AMD or RequireJS loader.
For example:
var _ = require('lodash');33 votes -
Use Json.Net contract resolver when using Linq to generate SQL queries
Member names in SQL queries generated from Linq currently look at the member for either a JsonPropertyAttribute or DataMemberAttribute. If the ability to specify custom JsonSerializerSettings is implemented (see http://feedback.azure.com/forums/263030-documentdb/suggestions/6422364-allow-me-to-set-jsonserializersettings ), this will need to be implemented to actually remove the need to annotate every member of your data object classes.
28 votes -
Support the LIKE clause / regex expressions in the queries.
Support the LIKE clause / regex expressions in the queries.
Sample
--SQL
SELECT *
FROM THINGS
WHERE serialNumber LIKE '%A0000%'27 votes -
25 votes
Can you please share your requirements on number of points per polygon in DocumentDB?
Thank you,
Aravind Ramachandran
Azure DocumentDB -
Add DateTimeOffset support
The DocumentDb engine should be able to recognize and properly order DateTimeOffset serialized fields.
21 votes -
Add built-in cast function for SQL queries
Need built-in function for casting string datatypes to INT, NUMBER, DOUBLE, etc. in SQL queries as our data loader is converting the number to string during document creation. We have a requirement to filter on numeric values in our application.
19 votes
- Don't see your idea?