Russ

My feedback

  1. 3,842 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    128 comments  ·  Azure Cosmos DB  ·  Flag idea as inappropriate…  ·  Admin →

    Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.

    Update.

    The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
    github.com/azure/azure-cosmos-dotnet-v3

    We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.

    Once that is released we will mark this feature as complete.

    Thank you for your patience and votes.

    Russ commented  · 

    This is an unusable implementation.

    As the skip/limit is done in the aggregation pipeline, my experience is that your RU cost will be 1/10 of the number of items returned from your filter. For example if 10,000 items are matched on your filter it will charge you 1000 RU's from the aggregation pipeline.

    If you have a large collection and you don't know how many records are going to be matched from a search criteria then you are in for some pain.

    I am going to have to move to a MongoDB database as this is just to much of a limitation.

  2. 417 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  11 comments  ·  API Management » Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. 1,781 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    69 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →

    We’re excited to announce that we are making this a lot easier with our preview of Autopilot. With Autopilot, Azure Cosmos DB will automatically manage and scale the RU/s of your containers based on the usage. This eliminates the need for custom scripting to change RU/s and makes it easier to handle bursty, unpredictable workloads.

    You can try out Autopilot in your Cosmos accounts by going to the Azure Portal and enabling the feature in the “Preview Features” blade.

    Russ commented  · 

    This really is mandatory as we are getting hit by peak loads that mean I have to have the RU's to match, a very expensive model.

    Russ supported this idea  · 

Feedback and Knowledge Base