Jason

My feedback

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

    We recently released support for client-side transactions in our .NET SDK.

    https://devblogs.microsoft.com/cosmosdb/introducing-transactionalbatch-in-the-net-sdk/

    We would like to get your feedback on this to understand if this meets your needs for transaction support. Please read our announcement and/or feel free to try our new support then please respond to this one question survey.

    https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR_Lrg0nxRBtErN-GyphxUs9UQ0c1STlJTDVOT1JXUzhYVkYzU1JZSU5BTi4u

    Thank you.

    An error occurred while saving the comment
    Jason commented  · 

    I don't like stored procedures. Please make this feature happen!

    Jason supported this idea  · 
  2. 830 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.

    Jason supported this idea  · 
  3. 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…

    Jason supported this idea  · 

Feedback and Knowledge Base