Nate

My feedback

  1. 203 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Azure Cosmos DB » MongoDB API  ·  Flag idea as inappropriate…  ·  Admin →
    Nate commented  · 

    Folks, while I support this - namely in the ability to get data back for the interval, I'd suggest using Polly with a back off policy (assuming .net). This isn't solely a problem with cosmos. Even if you have a retry interval, it's still the server's best guess - in the best case - or an arbitrary suggestion in the worst.

    Moreover, if you use queuing or service bus, you can effectively load level or self-throttle yourself.

    Nate supported this idea  · 
  2. 2,824 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    80 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →

    Azure Cosmos DB now supports GROUP BY queries! With GROUP BY, you can run queries that group your results according to the values of one or more specified properties. This feature is currently supported in Data Explorer, JavaScript SDK 3.4, and .NET SDK 3.3. Support for other SDKs will be available later this year.

    Nate commented  · 

    I'm sorry, but throwing in spark for the sake of a standard query capability seems a bit excessive, to put it mildly. This has been going on for nearly a year now - is it possible to get an actual ETA or update on this?

    I've been a big proponent of Cosmos and have used it in a number of projects for clients, but it's getting to the point of absurdity having to say "but it can't do that" - it's like a bad Meatloaf parody. Please get some of this core stuff addressed ASAP and/or provide regular updates. A year without delivery is a little underwhelming. Still waiting on autoscale RUs that were promised, as well, btw.

    Nate supported this idea  · 

Feedback and Knowledge Base