Diego Oliveira Sanchez

My feedback

  1. 124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →
    Diego Oliveira Sanchez supported this idea  · 
  2. 1,783 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    69 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →

    We want to share the great news that ADF has been added to the list of “Trusted Azure service” for Azure Key Vault and Azure Storage (blob & ADLS Gen2)!! Now you can enable “Allow trusted Microsoft services” on AKV and Azure Storage for better network security, and your ADF pipelines will continue to run. There are two caveats to pay attention to: (1) In order for ADF to be considered as one of the “Trusted Microsoft services” you need to use MSI to authenticate to AKV or Azure Storage in the linked service definition, and (2) If you are running Mapping Data Flow activity – “Trusted Azure service” is not supported for Data Flow just yet and we are working hard on it.

    What is coming up? Here are the additional enhancements we are making for better network security:
    - Static IP range for Azure Integration Runtime so that…

    Diego Oliveira Sanchez supported this idea  · 
    Diego Oliveira Sanchez commented  · 

    Is there a timeline for implementing this feature? Do you anticipate it will be ready in a few weeks, a few months, or a few years? What is the order of magnitude here?

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

    Diego Oliveira Sanchez commented  · 

    Related to @Vince who posted right before me. I am querying using the mongoDB API. I've noticed that querying the 3,000th item consumes many more RUs than querying the first few items. Like 50 times the amount of RUs. I am doing something like model.find(<query>).skip(3000).limit(25). Am I doing something wrong, or do we have to wait for the Cosmos team to implement an efficient skipping mechanism?

    Diego Oliveira Sanchez supported this idea  · 
  4. 4,131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    87 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Diego Oliveira Sanchez commented  · 

    any updates? We are ready to migrate to CosmosDb, but without this feature we would have to spend months rewriting half of our application. We have many simple operations (e.g. update a single value) that should take 3-4 RU, but because the documents are large, and Cosmos replaces the whole document, many of these simple operations consume 500+ RU, which doesn't work for us. Any updates would be appreciated.

    Diego Oliveira Sanchez supported this idea  · 

Feedback and Knowledge Base