This is currently not on our roadmap. However, we will continue to review this item in the future as we prioritize future releases.
Thank you for your suggestion.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
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.
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.Oleg Gliznutsa commented
Offset/Limit don't work correctly with EnableCrossPartitionQuery option - e.g. db returns first 15 results when requesting OFFSET 10 LIMIT 5
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
We are reviewing this feature request for our backlog. Thank you for your feedback.
Auto-scaling of reserved units is on the roadmap for Windows Azure Media Services.
We have started work on this feature. Will update here when this becomes generally available.
Thank you for your request and votes.Oleg Gliznutsa shared this idea ·
We’re excited to announce that we are making this a lot easier with our preview of Autopilot. With Autopilot, Azure Cosmos DB will automatically manage and scale the RU/s of your containers based on the usage. This eliminates the need for custom scripting to change RU/s and makes it easier to handle bursty, unpredictable workloads.
You can try out Autopilot in your Cosmos accounts by going to the Azure Portal and enabling the feature in the “Preview Features” blade.