Azure Cosmos DB

Have feedback for Azure Cosmos DB product? Submit your idea here or upvote other ideas. All feedback is monitored and reviewed by the Azure Cosmos DB team. 

This site is for feature suggestions only. For technical questions or issues, please submit them to StackOverflow,where we and the community can better help you.

Please use the following categories when submitting your idea.

SQL API: Query language features, syntax using SQL API, indexing, any other core features in Azure Cosmos DB.

Gremlin API: Graph features and capabilities using Gremlin API.

Cassandra API: Features and capabilities using Cassandra API.

MongoDB API: Features and capabilities using MongoDB API.

Table API: Features and capabilities using Table API.

Etcd API: Features related to using etcd as a configuration store for Kubernetes.

Azure Synapse Link: Features related to Azure Cosmos DBanalytical store and Azure Synapse Analytics run-time support

Built-in Notebooks: Features related to built-in Notebooks in Azure Cosmos DB.

SDK: Features related to Azure Cosmos DB SDKs for SQL API.

Change Feed: Features related to Change Feed.

Management: All management features, backup/restore,monitoring, ARM, PowerShell and CLI.

Portal: All features for Azure Portal and Cosmos DB Explorer.

Emulator: Features related to the Azure Cosmos Emulator.

Other: Features not related to any other category.

Security:
Authentication, authorization,permissions and encryption features.

Monitoring:
Metrics, monitoring, alerts,and diagnostics features.

Server-side: Stored procedures, Triggers,and User-Defined Functions.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Unique index in nested documents or arrays

    Right now I'm not able to create unique indexes in nested documents.
    Using MongoDB Driver.

    Error:
    {"ok": 0.0, "errmsg": "Unique index does not currently support nested documents or arrays.", "code": 115, "codeName": "CommandNotSupported"};

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  2. Azure cosmos DB: Mongo API with Mongo scala driver, cursor support

    When using mongo scala driver to query a collection, I used the process as below:
    - create a client;
    - get a database;
    - get a collection;
    - have mutiple find to query the collection;

    However, those find seems to have conflicts between each other since they might return either cursor *** is not found on server... or wrong value from the db. It's weird since the scala driver is async/non-blocking and multiple queries should be fine.

    It should be the issue of no cursor support on the cosmosDB side, so I wonder whether we can have this feature.

    Thanks.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Align the handling of Unique Sparse Indexes with MongoDB

    Currently, the Azure Cosmos DB Mongo API does not support sparse unique keys (https://docs.microsoft.com/en-us/azure/cosmos-db/unique-keys#define-a-unique-key). This is at odds with the current implementation of MongoDB which does support Sparse indexes with a unique constraint (https://docs.mongodb.com/manual/core/index-sparse/).

    Meteor, a popular framework using MongoDB, use sparse indexes with unique keys in its fundamental user management (https://github.com/meteor/meteor/blob/c5b51b0fc2a8cef498b9390ebcb4925e02de83e8/packages/accounts-base/accounts_server.js#L1562).

    The current implementation of MongoDB allows you to create documents (such as a user document) without a field that has a unique sparse index (such as username). This is not possible with the Azure Cosmos DB Mongo API, forcing you to populate…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add support for cursor.explain() method

    It would be nice if the cursor.explain() method worked, for troubleshooting performance of ad-hoc queries. Currently it returns empty data for the queryplanner information.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Need way to create collections via the Mongo DB API with a specified RU throughput

    Developers using the MongoDB API should be able to programmatically create collections of a given RU throughput, similar to the capability that the DocumentDB API already provides.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support Users and Roles management

    It should be possible to use the create/drop/getRole and create/drop/getUser for MongoDB API!

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow creating Index with weights

    It would be nice to have index capability with weights in Azure Cosmos Db through Mongo driver. Currently it says this feature isnt available. Something like how we do in MongoDB

    db.blog.createIndex( { name: "text", desc: "text", headername: "text" }, { weights: { content: 10, keywords: 5 }, name: "TextIndex" } )

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  8. Ability to refresh(copy) Cosmos DB from one instance to another

    Development teams often need data to be copied from one database instance to another e.g. copy all the data from a production database instance to a development/stage instance every other month or so. The current configuration does not allow an easy way to do this. It would be nice if you extend the functionality of the Azure Data Migration tool to take cosmos DB as source and another CosmosDB as a target to allow this. Though this can be achieved via the workaround of using mongodump which fails for bigger data loads due to the RU limits on cosmos Collections.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  9. MongoDB Query projecting optional fields

    Cosmos Mongo doesn't support the projection of optional nested fields.

    Suppose i have two documents like this
    {
    "id": 100,
    "name": "bruceLee",
    "specialSkills": {
    "combat": "hand2hand",
    "extendedLife": true
    },
    "level": 2
    }

    {
    "id": 101,
    "name": "john",
    "level": 0
    }

    In cosmos the below query is failing whereas in mongo it works fine. This is very useful for the complex json.

    db.getCollection('players').find({},{"id": 1,
    "name": 1,
    "level": 1,
    "specialSkills.combat": 1 })

    Because some don't have specialSkills I can't use this query.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support View objects similar to MongoDB

    Create the capability to create views similar to MongoDB database. Views are very useful when is required to do aggregation operations, lookups in different tables as well.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Return random for $sample

    $sample should return an actual random sample.

    Right now it returns the top/first N items. This is preventing us from porting code over the Cosmos DB.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  12. slice projection not working mongodb

    User.findById({ _id: req.params.id }).slice('blacklistGroup', [0, 2]).then((res) => { outputs slice must be an integer error. More details here https://stackoverflow.com/q/61290693/2683814

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  13. Cursor for a non-existent collection

    My partner is developing their service based FIWARE as OSS on Azure . They usually use mongoDB on on-premise. I would appreciate it if you could fix this difference between MongoDB and Azure CosmosDB mongodb API.
    This is their feedback as below :


    • In FIWARE Orion, there is a case to perform a find for a collection that does not exist, for example, for automatic collection generation, but in this case, it receives unexpected search results and fail.

    • [Difference between mongoDB and Azure CosmosDB mongo API]

      • [mongodb] The cursor found in a non-existent collection is empty, and false is returned…
    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base