[DocumentDB] Allow Paging (skip/take)
Allowing paging would be huge. Btw, Thank You for rolling out this feature at all! It looks wonderful! Can't wait to try it! However, I won't be able to use it for actual work projects until it supports paging and sorting.
Work on making this feature available in all SDK’s as well as cross-partition is now available so marking this as complete.
The team has seen your feedback regarding performance for queries with especially large OFFSET values and is currently working on optimizing these by better utilizing the index and further improving performance. These optimizations will be released shortly.
For more information on Offset/Limit please see, https://docs.microsoft.com/en-us/azure/cosmos-db/sql-query-offset-limit
Anthony BOUQUET commented
I need some updates too. paging is mandatory in our use case and we won't go on cosmo db until it will be featured.
Ezequiel Ramos commented
[Deleted User] commented
Lajos Marton commented
Finally, it will worth the money.
At this time, I can say we are working on some foundational pieces which will light up skip/take in future.
Without skip. I will not even bother with docdb. Its an absolutely essential thing. It seems funny to me it is not yet implemented. Must be difficult to achieve for some reason.
It’s interesting to note CosmosDB is promoted as a MonogDB compatible api yet skip is support on MongoDB and we seem to be getting nowhere quickly
Jason Kergosien commented
I have to agree with everyone. It's a big deal.
Even if it's not a typical NoSQL feature, it doesn't matter. I'm a convert to NoSQL thanks to Cosmos, but since I'm used to very good functionality with RDBMS, guess what, I expect a lot.
(You can only blame yourself (MS). You spoiled us with great features w/SQL Server :) )
Adoption has got to be a key metric for Cosmos, so this should be important to add.
My 2 cents. Thanks guys!
Update us on this, thank you
Pravin Kadam commented
Any Updates on this?
Hi, still no update to SKIP support ?
Hello, any update on this?
It's been 3.25 years. How long does it take to implement this? We want to switch from RavenDB, but CosmosDB just has too many limitations.
Rob Teixeira commented
Seriously? Still no update to this in over a year? Lack of Skip just torpedoed Cosmos DB for my project. Back to SQL Azure...
Justin Staffer commented
Skip is a big deal for us. LINQ is too slow and we would need to pull a ton of data. Please correct me if I'm wrong.
william lee commented
Will you tell us where you guys are on this? thanks much
Bryce Godfrey commented
Not only skip/take but also the total count in the result set would be beneficial. The example of a list of records where I need to show the total count and let the user page through them.
Now that the Microsoft Build event has ended, can we get an update on this?
Sibin S commented
Its been 3 years :) Common this would be a great addition to it.
Where is this at? What are we supposed to do until this point? Pull the entire data set back and page it in code?