How can we improve Azure Cosmos DB?

[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.

3,786 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Fred Steffen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

124 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • che commented  ·   ·  Flag as inappropriate

    This would be super helpful when driving a UI straight from DocumentDB. The primary rule of scaling any UI to handle millions of records is to implement paging everywhere. Please don't implement it with continuation tokens the way Azure Table Storage did. That's very hard to consume in a UI. You have to store the previous token in a session (which is not scalable) so the user can navigate backwards. Plus, there's no way to tell the user how many pages there are total.

    An implementation more akin to SQL's skip/take/limit would be much more usable. Also, pagination is not very useful unless it can also be ordered by some criteria. Therefore, please remember to include an "order by" clause that can be used in conjunction with the skip/take/limit clause.

  • che commented  ·   ·  Flag as inappropriate

    This is needed for paging scenarios. This would be much more powerful if we had "order by" and "skip" commands to use in conjunction with a "limit" command.

  • Luis Delgado commented  ·   ·  Flag as inappropriate

    implement the capability to limit the results that come back from the Azure DocumentDB collection, for example, 'LIMIT 1000' will return only the first 1000 rows the meet the query filter.

1 2 3 4 5 7 Next →

Azure Cosmos DB

Feedback and Knowledge Base