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.

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

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. Cosmos DB Linux ODBC Driver

    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.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support for "Search text" ($text Operator)

    Support for "Mongo Search Text" (https://docs.mongodb.com/manual/text-search/). Example of use:

    db.stores.find( { $text: { $search: "java coffee shop" } } )

    89 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add ability to rename databases and collections

    It should be possible to rename databases and collections.

    This feature is universal in all if not the vast majority of database products.

    Lack of ability to rename anything makes it very hard for us to manage releases if we are adding new data. Currently, we have to create a copy of the existing database (which is a feat in itself, since this again is not core functionality), make the change there, and then re-point the website to the updated database. All this time, we are incurring extra costs and inconvenience.

    Renaming things also allows us to correct typos, which…

    400 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Management  ·  Flag idea as inappropriate…  ·  Admin →

    The ability to rename databases and collections is not currently something that is in our road map.

    Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.

    Thanks for your request and input on this. We may consider this for a future planning cycle.

    thanks.

  6. 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.

    490 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support documents up to 16mb

    It's not possible to migrate documents greater than 2mb, please consider increase document size up to 16mb

    110 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 →
  8. 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.

    296 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →
  9. Execute read-only stored procedures on secondary replica

    I have a many-to-many scenario close to the post below:
    https://feedback.azure.com/forums/263030-documentdb/suggestions/6611247-support-cross-document-joins
    I have multiple entities, and the relationships between them are saved as documents and can't be denormalized.
    Instead of doing multiple queries against the DB, I'd like to wrap it in a stored procedure to save round-trip time.
    However, current stored procedures can only execute on primary replica, so it would be slow if the users are from another region.
    Is that possible to define some read-only stored procedures so that it can be executed in read regions?

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  10. Like upsert, add a get or add function

    like ConcurrentDictionary, there is a GetOrAdd function,

    I frequently find my self doing the following
    1. Check if Document exists
    2. If not, Add document

    Since this is a non-atomic action, today I have to write stored procedures to do this safely.

    possible prototypes

    GetOrAdd(string id, DOC doc)
    GetOrAdd(Expression<Func<DOC, bool>> where, DOC doc)

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Built-in OAuth support

    Support OAuth to make it easy for mobile clients to securely talk directly to DocumentDB without a middle tier or a separate resource token broker.

    206 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  12. JDBC Support

    Provide a JDBC adapter to allow for multiple out of the box data solutions to connect to DocumentDB, ex TIBCO Business Works, SAS Reporting/BI, and Tableau.

    This would really open up use case possibilities.

    59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SDK  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add the ability to delete ALL data in a partition

    In a partitioned collection, it would be useful to have the option delete all data with a given partitionId.

    396 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  14. Increase 10GB limit on non partitioned collection

    Give there is a hard 10GB limit on a non-partitioned collection, and partition collections are much more expensive, with no auto-upgrade and code changes required to migrate to partitions, a larger size limit on non partitioned collection is much needed.

    81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. Make triggers be able to fire from Azure portal

    Triggers in DocumentDB should act like triggers in SQL Server, which means when you update documents from Azure portal, the triggers should be fired as well. Right now, this feature is missing. Triggers only can be fired from application code.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  16. Official ruby support

    Other document databases support ruby or have robust community support for ruby. Azure DocumentDB has neither. This is a show stopper for ruby shops. We're not going to pick a backend tech with zero official support.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SDK  ·  Flag idea as inappropriate…  ·  Admin →
  17. User Defined Document Functions (UDDF)

    Let's say you have some denormalized data:
    { id: '1, title: 'A story, userID: '1000' }
    { id: '2, title:' 'An article', userID: '1001' }
    where the userID field is denormalized into "user" documents.

    Since there are no cross-document joins, you have to loop result sets either in a DocumentDB Procedure or in the client to populate the 'user' data in the above example.

    There are several scenarios where looping result sets in a Procedure is the only viable solution (as opposed to looping on the client). This could be either performance and RU concerns, or simply network latenzy problems.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →
  18. Sub-collections for multi-tenant applications

    In a multi tenant environment it is absolutely essential to limit results only to documents that belong to the current tenant. Adding a tenant name property to every document is not good enough because developers must ALWAYS remember to filter queries by that property. If they forget to do that the results can be devastating. It is also not possible to prevent that with tests.

    To use a separate collection for each tenant is too expensive with the current pricing structure.

    Please enable a possibility to add sub-collections that would act as a query boundary. They should also be a…

    107 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  SQL API  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your suggestion. This is not currently on our road map.

    As suggested by others, customers are implementing this pattern using the same container with a partition key per tenant or a synthetic key with the tenant id and one or more other properties.

    Will mark this as unplanned and leave open and will revisit this in future planning cycles.

    Thank you for your suggestion and votes.

  19. Provide Django integration example

    Provide an example of utilizing DocumentDB with Django. Even better would be showing the replacement of the default sqlite db in Django with DocumentDB.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SDK  ·  Flag idea as inappropriate…  ·  Admin →
  20. AzureML Reader Module

    Create a Reader module in AzureML that can use DocumentDB as a data source.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Cosmos DB

Categories

Feedback and Knowledge Base