If you have to deal with a large number of documents when doing queries against a Couchbase cluster it is important to use pagination to get rows by page. You can find some information in the documentation in the chapter “Pagination”, but I want to go in more details and sample code in this article.
For this example I will start by creating a simple view based on the
beer-sample dataset, the view is used to find brewery by country:
1 2 3 4 5
This view list all the breweries by country, the index looks like:
So now you want to navigate in this index with a page size of 5 rows.
Using skip / limit Parameters
The most simplistic approach is to use limit and skip parameters for example:
Page 1 :
Page 2 :
Page x :
You can obviously use any other parameters you need to do range or key queries (
startkey/endkey, key, keys) and sort option (
This is simple but not the most efficient way, since the query engine has to read all the rows that match the query, until the skip value is reached.
Some code sample in python that paginate using this view :
This application loops on all the pages until the end of the index.
As I said before this is not the best approach since the system must read all the values until the skip is reached. The following example shows a better way to deal with this.
Using startkey / startkey_docid parameters
To make this pagination more efficient it is possible to take another approach. This approach uses the
startkey_docid to select the proper documents.
The startkeyparameter will be the value of the key where the query should start to read (based on the last key of the “previous page”
- Since for a key for example “Germany” you may have one or more ids (documents) it is necessary to say to Couchbase query engine where to start, for this you need to use the
startkey_docidparameter, and ignore this id since it is the last one of the previous page.
So if we look at the index, and add a row number to explain the pagination
|Row num||Doc id||Key||Value|
Query for page 1
Query for page 2|
Query for page 3
So as you can see in the examples above, the query uses the startkey, a document id, and just passes it using skip=1.
Let’s now look at the application code, once again in Python
This application loops on all the pages until the end of the index
Using this approach, the application start to read the index at a specific key (
startkey parameter), and only loop on the necessary entry in the index. This is more efficient than using the simple skip approach.
Views with Reduce function
When your view is using a reduce function, if you want to paginate on the various keys only (with the reduce function) you need to use the
When you are using the paramater
startkey_docid with a reduce function it will calculate the reduce only to the subset of document ids that are part of your query.
Couchbase Java SDK Paginator
In the previous examples, I have showed how to do pagination using the various query parameters. The Java SDK provides a Paginator object to help developers to deal with pagination. The following example is using the same view with the Paginator API.
So as you can see you can easily paginate on the results of a Query using the Java Paginator.
- At the line #37, the Paginator is created from using the view and query objects and a page size is specified
- Then you just need to use the hasNext() and next() methods to navigate in the results.
The Java Paginator is aware of the fact that they query is using a reduce or not, so you can use it with all type of queries - Internally it will switch between the skip/limit approach and the doc_id approaches. You can see how it is done in the Paginator class.
Note that if you want to do that in a Web application between HTTP request you must keep the Paginator object in the user session since the current API keeps the current page in its state.
In this blog post you have learned how to deal with pagination in Couchbase views; to summarize
- The pagination is based on some specific parameters that you send when executing a query.
- Java developers can use the Paginator class that simplifies pagination.
I am inviting you to look at the new Couchbase Query Language N1QL, still under development, that will provide more options to developers including pagination, using LIMIT & OFFSET parameters, for example:
1 2 3 4 5
If you want to learn more about N1QL: