Zach

My feedback

  1. 248 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Azure Cosmos DB » Change Feed  ·  Flag idea as inappropriate…  ·  Admin →
    Zach supported this idea  · 
  2. 502 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…

    An error occurred while saving the comment
    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. 831 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 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  · 

Feedback and Knowledge Base