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.

How can we improve Azure Cosmos DB?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Problem with Gremlins API

    I have problems when i send a series of query to the dbs, the response arrived after a long time. How can i resolve it?

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
  2. Azure IAM - Cosmos DB Account Reader Role

    The "Cosmos DB Account Reader Role" is set to "Can read Azure Cosmos DB Accounts data" with following read actions:

    Microsoft.Authorization/*/read
    Microsoft.DocumentDB/databaseAccounts/*/read
    Microsoft.DocumentDB/databaseAccounts/readonlykeys/action
    Microsoft.Resources/deployments/*
    Microsoft.Resources/subscriptions/resourceGroups/read
    Microsoft.Support/*

    So if my understanding is correct, it should not allow creating new Stored Procedure/Trigger/UDF. This role works fine in Collections --> Script Explorer section where Create Stored Procedure/Trigger/UDF button is disabled. However, in Data Explorer section New Stored Procedure/Trigger/UDF button is enabled and it allows a user with IAM "Cosmos DB Account Reader Role" to create new Stored Procedure/Trigger/UDF.

    A user should have same access in all sections as per IAM "Cosmos DB Account…

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Godrej Azure Virtual Machines

    Find new and under construction projects by Godrej Group - Find furnished or unfurnished flats/apartments at an affordable price

    https://www.weplanithk.com/project/godrej-properties/11/

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  4. fix combined path lenght for unique indexes

    Stated in the documentation "combined paths for all unique index properties should not exceed 60 characters"

    But when creating the following Index

    db.Commits.createIndex(
    {
    "BucketId" : 1,
    "StreamId" : 1,
    "StreamRevisionFrom" : 1,
    "StreamRevisionTo" : 1,
    }, {unique: true})

    I take the above to be 49 characters.

    The following error is returned

    "Make sure that the property names do not contain invalid characters and that the combined paths for all unique index properties do not exceed 60 characters.\"

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Update documentation on enabling Gremlin queries on HDInsight via CosmosDB connector

    The documentation on how to enable Gremlin queries on HDInsight via the CosmosDB Spark connector should be brought up-to-date.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Partition switching between collections and databases.

    I have a requirement to ingest documents into an ingestion collection. Once the documents are processed I'd like to do bulk moves of documents from the ingestion collection to archive collections. I think a feature like partition switching in SQL Server would work really well for Cosmos DB. At the moment I have to consider copying the appropriate documents from the ingestion collection using the bulk executor then once successfully copied delete the documents from the ingestion collection.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hello Graeme. Currently we do not offer this functionality in precisely the way you have asked for.

    However, customers are using our Change Feed feature to archive off data and otherwise manage data between an ingest container and other colder storage. You can take a look here to learn more about Change Feed. This may be actually what you’re after.

    https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed#change-feed-use-cases-and-scenarios

    Let us know and thanks!

  7. provide $ position support in mongodb

    It is very tough to query inner json without $ support

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 2D geometry support

    Although some users are excited about using CosmosDB, they are blocked from adopting it if their systems work with 2D geometry, which CosmosDB does not support. CosmosDB should support 2D geometry.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Fix sort results when documents are missing sort field

    When documents are missing the sort field, they should still be included in the query results. Cosmos DB with MongoDB API omits these documents, but MongoDB includes them.

    For example, the following query will return people sorted by age, but documents missing the age field do not appear in the results:

    peopleCollection.find().sort({ age: 1 })

    This is probably related to the following Cosmos DB with SQL API issue: https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/16842499-order-by-null-handling. Will resolving that issue fix MongoDB sorting as well?

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  10. Extend Bulk Executor to cover Cosmos Db Table Api

    Bulk Executor api is very powerful but does only support Document db. We would ideally want to use Table api because Document db api does not support OData. But we also work with a high throughput in a big data pipeline where we use Bulk Ingestor api to do the data ingestion which does not work in Table api. It would be nice to have same bulk ingestion functionality for Table api

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Table API  ·  Flag idea as inappropriate…  ·  Admin →
  11. DBCC CHECKDB

    Given how poor the backup\restore process is in terms of only having 8 hours to preform a restore, it would be really useful to make available the equivalent of SQL DBCC CHECKDB.
    If the equivalent is already being run as part of cosmos DB services already, then documentation should be made available so customers are aware of it. And aware of what to do when it reports any corruption.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for checking the API type of account in .Net SDK

    Currently .Net SDK allows to upload documents to MongoAPI CosmosDB Account. But not able to see the data in the explorer. It shows error and charge for the data stored. This can happen if someone install the application by creating wrong API typed account.
    Need option in .Net SDK to check the API Type of the account if the account url and keys are available. Or throw some meaningful errors when wrong account is used when writing data.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  13. Able to view entire graph in the data explorer

    I would like to be able to view my entire graph in the data explorer. At least this should be possible for small graphs. Right now as you traverse, the explorer removes the previous nodes from the graphical view. This is really a pain for small graphs where you want to view the complete the picture. I can understand the new for big graphs but for small ones you should allow displaying the entire graph.

    Also, it should be possible to view edge properties on the data explorer without looking at the tab view.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. Bug: Query with MAX aggregation shows 0 RU in Data Explorer

    When running a query such as shown below on a partitioned collection, it always returns 0 RU even though it may take a fair amount of time to compete (occasionally is will return no data even though there is data there). Running the same query on a non-partitioned collection does return a non-zero RU value.

    SELECT VALUE MAX(c.timestamp) FROM c WHERE ....

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  16. Portal: Scale & Settings does not update

    This happens if you use code to update the throughput of a collection.

    In the Portal, under Data Explorer -> Scale & Settings the value does not change unless you refresh the whole portal (eg press F5).

    Even if you close and re-open the "Scale & Settings" tab the value will not change.

    It would be better if the the "Scale & Settings" tab checked the current throughput value when you open the tab.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  17. DocumentDB SDK for Node.js should allow agent or maxSockets to be set for outbound requests

    The DocumentDB SDK for Node.js should allow an agent or maxSockets to be set for outbound requests.

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. DocumentDB Migration tool should not default JSON casing when choosing DateTime Both option

    I am experimenting with the migration tool and found that when I chose the Persist Date and Time as Both option it created JSON properties with capitalized casing. It would be useful (and probably pedantic) to be able to control that casing since these are generated properties.
    E.g.

    "created": {
    "Value": "2013-04-08T20:41:12.9630000",
    "Epoch": 1365453673
    },

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. BUG: Problem with spatial queries against LineString

    Query such as below returns nothing when geojson type = "LineString" (Point is ok):

    SELECT * FROM c WHERE ST_INTERSECTS(c.geojson, <hardcoded polygon geojson>)

    However, query like this will work as expected:

    SELECT * FROM c WHERE ST_INTERSECTS({type: c.geojson.type, coordinates: c.geojson.coordinates}, <hardcoded polygon geojson>)

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
1 2 9 10 11 13 Next →
  • Don't see your idea?

Azure Cosmos DB

Feedback and Knowledge Base