[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
WE NEED THIS NOW! GET IT DONE.
Steve Haran commented
Really need to implement paging - it seems like the most basic of requirements. Please - any updates?
Why is this taking so long? This has been kicking around for ages now.
Question: What is the utility of DocDb if you can't page through results in large datasets?
Any ETA or Update, DoumentDB is a great product. Although without proper paging support (Page forward and Back, get specific page etc) its use in web applications is limited.
So, how far is this?
The link by Henrik Ebbeskog shows how to iterate, but not how to page. (Paging is when the user can go to the previous or next page in a view.)
Furthermore, for a collection to use min/max requires some unique sortable property, which many collections don't have.
(Many have either unique or sortable, but not both.)
Hey folks, this has been in the planned state for almost a year now. Can we please get an update on what that means? Our teams are using DocumentDB in a limited capacity right now and having this feature would be a significant win. I know there are alternatives, but they are messy at best compared to a clean skip implementation. - M@
Amit Chaudhary commented
Any update on the support for advance paging via skip/take?
Henrik Ebbeskog commented
Michael Rajesh commented
skip/take? Currently you can go with TOP at select and use WHERE with c._ts and an ID field (/ what you use in ORDER BY) of the previous page least or maximum values..
really needs to work with partitions too
Ian Moores commented
Any update on this??
Dieter Goetelen commented
When is this feature about to releast? This is a showstopper for us to use documentDB as for many people I guess. Not sure how to use documentDB without paging support/avg functions..
Any update on Skip/Take for paging. when is this going to be supported?
Any updates to SKIP/Take
Alin Becea commented
Any update on SKIP/TAKE feature release?
Tim Genge commented
So we spent 2 week transferring our significant database of events across to DocumentDb from SQL, with some great UPSERT improvements.
RU limitations, lack of aggregate functions without expensive SPs and the lack of SKIP is however pretty untenable. We may have to return to SQL!
Come on DocumentDb devs, sort it out. Like ODATA, this is another throw away technology MS really isn't putting the correct resources into.
please implement skip and get rid of continuation token
Gustavo Tandeciarz commented
TOP is great, but we still need Skip in order to implement paging. So this is 50% done.
Rush Frisby commented
@Han Did you mean SKIP instead of TOP?