We are looking at this but it is not in our immediate roadmap. Will update on whether we add this to our roadmap.
Thank you for your suggestion.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.
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.