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

    389 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  SDK  ·  Flag idea as inappropriate…  ·  Admin →
  2. store asp.net session state in azure documentdb

    i want store asp.net session state in azure documentdb.
    I remember there was a special store provider for appfabric cache to store session state (configured in web.config), it's also possible with sql server. however, in documrntdb you can't do this, if i use documrntdb as my main db and im using an adhoc loadbalancer it will be great to store the asp.net session state in documrntdb.

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

    We have recently worked with the ASP.NET team to update the ASP.NET Session State Provider for Cosmos DB. This provider fixed a major limitation in only allowing for 32 logical partitions which severely limited it’s ability to scale to large numbers of users.

    Customers are welcome to try this updated provider for regular ASP.NET as well as the ASP.NET provider for .NET Core.

    https://github.com/aspnet/AspNetSessionState

    Thank you.

  3. Allow consumption of Change Feed as a in-memory push model in SDKv3

    Unlike the older SDK, the SDKv3 doesn't support the InMemory Lease Container yet. But this is very useful e.g. if you just want to use the ChangeFeed to keep your local caches up2date.

    This is also described here: https://github.com/Azure/azure-cosmos-dotnet-v3/issues/972

    3 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 →
  4. 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…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK  ·  Flag idea as inappropriate…  ·  Admin →

    This is supported now. We don’t have a proper sample, but you can pass a custom agent to the constructor

    https://github.com/Azure/azure-sdk-for-js/blob/master/sdk/cosmosdb/cosmos/src/CosmosClientOptions.ts#L45

    Here is a rough sample you can use:

    const https = require(“https”);
    const { CosmosClient } = require(“@azure/cosmos”);

    const agent = new https.Agent({
    keepAlive: true,
    maxSockets: 20
    });

    const endpoint = “…”;
    const key = “…”;

    const client = new CosmosClient({
    agent,
    endpoint,
    key
    });

    client.databases
    .readAll()
    .fetchAll()
    .then((response) => {
    console.log(response.resources);
    });

    Thanks.

  • Don't see your idea?

Feedback and Knowledge Base