Spring Data Elasticsearch如何使用offset和limit进行分页查询？

Hey there! I get where you're coming from—trying to use offset/limit for pagination in Spring Data Elasticsearch but hitting a wall with the PageRequest API. Let's break this down and fix it.

Why PageRequest Doesn't Support Direct Offset Input #

The PageRequest.of(pageIndex, pageSize) method is built for page-based pagination, not raw offset/limit. Spring Data's Pageable abstraction is standardized across different data stores (like JPA, MongoDB), where page-based pagination is the common pattern. That's why there's no out-of-the-box method to pass an offset directly.

Solution 1: Convert Offset/Limit to Page Index/Size #

If you still want to use the Page return type, you can calculate the page index from your offset and limit with a simple formula:

int offset = 20;
int limit = 10;

// Calculate zero-based page index
int pageIndex = offset / limit;

// Create PageRequest with converted values
PageRequest pageRequest = PageRequest.of(pageIndex, limit);

// Execute your query as usual
Page<Content> contentPage = elasticsearchOperations.queryForPage(
    new NativeSearchQueryBuilder()
        // Add your query conditions here (e.g., matchAllQuery())
        .withPageable(pageRequest)
        .build(),
    Content.class
);

Note: This works seamlessly when your offset is a multiple of the limit. If your offset isn't aligned (e.g., offset=25, limit=10), you'll need to manually slice the result list from the returned page to get the exact subset you need.

Solution 2: Use Elasticsearch's Native From/Size Parameters (Recommended) #

Elasticsearch natively supports from (offset) and size (limit) parameters, and Spring Data Elasticsearch lets you use them directly with NativeSearchQuery:

int offset = 20;
int limit = 10;

NativeSearchQuery query = new NativeSearchQueryBuilder()
    // Add your query conditions here
    .withFrom(offset)
    .withSize(limit)
    .build();

// Get results starting exactly at your offset
List<Content> contentList = elasticsearchOperations.queryForList(query, Content.class);

// If you need a Page object (with total count metadata), build it manually:
long totalCount = elasticsearchOperations.count(query, Content.class);
Page<Content> contentPage = new PageImpl<>(contentList, PageRequest.of(offset/limit, limit), totalCount);

This approach skips page index conversion entirely and mirrors Elasticsearch's native pagination behavior directly. It's the most straightforward way to implement offset/limit-based queries.

Key Takeaway #

While Pageable is great for page-focused workflows, if you need strict offset/limit control, using withFrom() and withSize() on NativeSearchQueryBuilder is the optimal choice. You can still construct a Page object afterward if you need total count metadata for your UI or reporting.

内容的提问来源于stack exchange，提问作者Michael