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.
-
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.
559 votesWork on Bytecode support has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
-
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.
441 votesThis is currently not on our road map. However, we will review this item in the future as we prioritize future releases.
-
Implement a graphql provider
graphql {http://graphql.org/} is becoming increasingly adopted by front end frameworks (including mobile) for querying backend / API data.
Rather than having to translate each graphql query into a DocumentDB client call it would be optimal and very powerful to issue the query directly.
It would also provide enhanced query abilities over the existing REST approach.
274 votesApologies for the confusion on our part.
This is currently not on our roadmap. However, we will review this item in the future as we prioritize future releases.
Thanks for your suggestion.
-
Support Gremlin APIs on Cosmos DB Emulator
The Cosmos DB Emulator currently does not support the Gremlin API. So at the moment it is not possible to test against the emulator using the Gremlin Console (http://tinkerpop.apache.org/docs/3.2.5/tutorials/the-gremlin-console/)
180 votesWe are currently working on this. Expect release before end of 2018.
Thank you.
-
Gremlin queries from stored procedures
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.
105 votesThis is now on our road map and is planned for our Fall development semester.
Thank you for your suggestion and votes.
-
Support for W3C SPARQL as a query language
SPARQL is a mature W3C standard for querying and updating graph-like data with well defined semantics and rich query capabilities.
103 votesWe don’t have any plans for SPARQL yet. We will keep this on our backlog and track user interest here as we prioritize upcoming work sprints.
Thanks.
-
Unique indexes on Graph vertex/edge properties
I need to ensure global uniqueness for things like username/email/mobile number/etc. Since we no longer have traditional SQL, this capability is lacking. Allow me to define unique indexes so the write region has only one occurrence of a distinct value.
Ideally, this should also make FILTERED unique indexes possible.
61 votesThis is currently not on our road map. But we will revisit this again in our next review.
Thank you for your feedback.
-
Support for Graph API in Data Migration tool
Looking for a way to do backup/restore or manual export/import of a Cosmos DB graph using Graph API - or equivalent.
I want to be able to restore state of a database while developing and found that Data Migration tool can do what I want, but does not support Graph API.48 votesThis is currently not on our road map. But we will revisit this again in our next review.
Thank you for your feedback.
-
Microsoft join and support GQL
I think it would be a great benefit for Cosmos DB to support the new movement to get to a single Graph Query Language. Microsoft joining this movement might help in rapid evolution and acceptance of such a language.
Taken from https://neo4j.com/blog/time-for-single-property-graph-query-language/:
The time has come to create a single, unified property graph query language.
Different languages for different products help no one. We’ve heard from the graph community that a common query language would be powerful: more developers with transferable expertise; portable queries; solutions that leverage multiple graph options; and less vendor lock-in.
One language, one skill set.
…
47 votesSupport for this is not on our roadmap but will mark as unplanned and leave open for future consideration.
Thank you for your suggestion.
-
add spatial support to Graph API
Enable the same support for spatial queries that exists for DocumentDb for graph elements. Similar to Neo4j Spatial.
34 votesThis is not in the Tinkerpop specification. We have no plans to add support to this just yet.
We will revisit this in the future however.
Thank you for you feedback.
-
CosmosDB Graph API should support array types inside Gremlin properties
Currently, the CosmosDB Graph API does not support array types inside of Gremlin properties. This forces users to rebuild their graph models to match what the Graph API requires. The CosmosDB Graph API should support array types inside of Gremlin properties.
19 votesWe’ve evaluated this request and at this time we are deferring this from our road map. Will leave this as open so we can consider this in the future.
Thanks.
-
Support for schemas (full, mixed and none)
Support schema-full and schema-mixed modes like OrientDB. This way one can _design_ a graph with vertex and edge classes. This is extremely useful when modelling known domains and removes all burden to do this in code.
18 votesCosmos DB is intended to be a schemaless database so we don’t support schemas in general. Support for this is not on our roadmap but will mark as unplanned and leave open for future consideration.
Thanks for your suggestion.
-
Support strategies on graph traversals
Currently, the graph traversal in Cosmos DB graph (usually referenced by 'g') does not support the 'withStrategies'-method that is normally part of a Tinkerpop implementation. 'withStrategies' allows e.g to enhance the traversal with custom vertex- and edge-filtering on every step (by a SubgraphStrategy).
14 votesOur apologies. This was mistakenly marked as Started.
We need feedback on this suggestion to evaluate for consideration.
We support Partition and Projection strategies, but not the rest. Can you provide more details on your use-case?
Thank you.
-
Improve range() step costs
Graph API is nice, however in its current state it is unusable for large data sets due to high RU costs.
We are trying to implement paging for retrieving large amounts of data, however RU cost is unacceptable. Query "g.V().range(0,100)" costs 63.11 RU, however "g.V().range(2000,2100)" costs 338.06 RU even though it is same amount of data. Higher values are even more expensive meaning it's impossible to retrieve high amount of data without scaling up throughput.14 votesThis is tied to our support for Skip/Take in Cosmos DB (https://feedback.azure.com/forums/263030/suggestions/6350987). This work has started. Once the underlying capability has been released this is something we will look at for Graph API.
Thank you for your suggestion.
-
Gremlin Graph: Add support for array values in group() and groupCount()
You should be able to group by an array of values. it is perfectly valid to do a group() or groupCount() like so:
g.V().groupCount().by(values('id','name').fold())
Other Graphs implementing Gremlin will give you a result, while CosmosDB fails with:
"Unexpected Error: Cannot resolve object to a primitive value."
13 votesWe have reviewed this request and at this time this is not on our road map.
Will leave this open and review this in upcoming cycles for our road map.
Thanks.
-
Allow me to create global read replicas with different partition keys
There is really no way to come up with a single partition key for my graph database to satisfy all queries. Some queries would benefit from a different partition key, so why not let people create copies of their whole graphs with different partition keys and give them a way to intelligently route queries to the correct server?
one write region with partition key A
multiple read regions with partition key A
multiple read regions with partition key B
multiple read regions with partition key C
...In other words, there would still be a single write region but multiple…
13 votesThis is something you can do this yourself with change feed to replicate a specific range or partition key to a different account.
To learn more about ChangeFeed, start here, https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed
Thanks for your suggestion.
-
Document how to make & use Icon Sets in the Graph Data Explorer
You have a Gremlin Graph Intro video that includes use an icon set (the video shows an icon set for Marvel characters) - but there is very little info on how you can create this icon set - i.e. the video shows a vertice that represents the icon set, but it isn't clear what properties on the vertice do what - and also what encoding is used for the icon picture content.
11 votesWe are planning on documenting this. Will update here when this is available.
Thank you.
-
Support lambda steps
Lambda steps (i.e. steps that take arbitrary groovy-functions as arguments) are currently not supported. We plan to migrate to CosmosDB but have a few traversals that contain lambdas.
10 votesSupport for this is not on our roadmap but will mark as unplanned and leave open for future consideration.
Thank you for your suggestion.
-
Gremlin console in Azure portal
Currently the option to do search queries in azure portal with gremlin is very slow. To avoid the setup of a local Gremlin console, it would be an improvement to have a gremlin console integrated into the portal. No need to specify connection string and keys, just ready to use and fast.
Would same time to each developer and be a frictionless no setup, just ready to use.
10 votesWe have reviewed this request and at this time this feature is not on our road map.
Will leave this request open so people can continue to vote and comment on it.
Thank you for your suggestion.
-
Support Math functions in the graph
simple arthimatic (like computing %s) have to be done after extracting the data. pl support math step
9 votesWe are reviewing adding this capability. There is no ETA on if or when it will get on our roadmap but will update here when status changes.
Thank you for your suggestion.
- Don't see your idea?