Zach

My feedback

  1. 217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Azure Cosmos DB » Change Feed  ·  Flag idea as inappropriate…  ·  Admin →
    Zach supported this idea  · 
  2. 493 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. I have discussed this in more detail with our team.

    You are correct the workaround suggested to use .AsEnumerable().FirstOrDefault(). should not be a recommended work around. This way results in materializing all documents on the client first before getting the 1st document, which is not very efficient and the exact opposite of what you are trying to achieve.

    Instead we recommend you use Take(1).AsEnumerable() and then .First() or .Single() or .FirstOrDefault() for Single() and First(). Take(1) is translated to SELECT TOP 1 and is processed server-side so more efficient than the previous suggestion and is what you are trying to achieve.

    As to the original ask. The support for these operations can be done, but this work is not prioritized against the other work we want to deliver. I will move this back as unplanned but please note this is on our roadmap.

    Thanks again…

    Zach commented  · 

    This is a simple request yet it's not being prioritized. Why can't we expect a modern DB to handle such requests? Please work on this.

    Zach supported this idea  · 
  3. 676 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  Azure Cosmos DB » Gremlin API  ·  Flag idea as inappropriate…  ·  Admin →

    Update on this item.

    Bytecode implementation is now targeting the first half of 2020 to provide stability and performance improvements in the platform.

    Apologies for the delay. We are continuing to work on this. Will announce here when this becomes available.

    Thanks.

    Zach supported this idea  · 
  4. 3,841 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.

    Zach commented  · 

    Microsoft is notorious for creating half-baked products and customer lock-in. Now, we're stuck waiting for this feature.

Feedback and Knowledge Base