Tablestore:Perform sorting and paging

Scenarios

Specify a sorting method when you create a search index

By default, data in a search index is sorted based on the value of the IndexSort parameter. When you use a search index to query data, the value of the IndexSort parameter determines the default order in which the matched data is returned.

When you create a search index, you can specify presorting settings by configuring the IndexSort parameter. If you do not specify presorting settings, data in the search index is sorted by primary key.

Specify a sorting method when you query data

Sorting can be enabled only for fields for which the enableSortAndAgg parameter is set to true.

You can specify a sorting method for each query. Search index-based queries support the following sorting methods. You can also specify multiple sorting methods based on different priorities.

ScoreSort

SearchQuery searchQuery = new SearchQuery();
searchQuery.setSort(new Sort(Arrays.asList(new ScoreSort())));

PrimaryKeySort

You can use PrimaryKeySort to sort the query results based on the value of the primary key.

SearchQuery searchQuery = new SearchQuery();
searchQuery.setSort(new Sort(Arrays.asList(new PrimaryKeySort()))); // Sort the query results in ascending order. 
//searchQuery.setSort(new Sort(Arrays.asList(new PrimaryKeySort(SortOrder.DESC)))); // Sort the query result in descending order.

FieldSort

You can use FieldSort to sort the query results based on the values of one or more specific columns.

SearchQuery searchQuery = new SearchQuery();
searchQuery.setSort(new Sort(Arrays.asList(new FieldSort("col", SortOrder.ASC))));

SearchQuery searchQuery = new SearchQuery();
searchQuery.setSort(new Sort(Arrays.asList(
    new FieldSort("col1", SortOrder.ASC), new FieldSort("col2", SortOrder.ASC))));

/**
* Sort the query results based on the values of the Col_Long column in descending order. If the data in the Col_Long column of the Long type is missing, you can use the Col_Long_sec column of the same data type as the supplemental column for sorting. 
*/
SearchQuery searchQuery = new SearchQuery();
FieldSort fieldSort = new FieldSort("Col_Long");
// Specify the Col_Long_sec column as the supplemental column for sorting when the data in the Col_Long column is missing. 
fieldSort.setMissingField("Col_Long_sec");
fieldSort.setOrder(SortOrder.DESC); 

// The doc1 and doc2 rows contain the field1 column of the Array type. The value of the field1 column in the doc1 row is [2,3] and the value of the field1 column in the doc2 row is [1,3,4]. 
// You can specify the mode parameter to determine the elements of the Array field in the two rows that are used to sort the two rows. 
{
    // If you set the mode parameter to SortMode.MAX, the maximum elements of the Array field are used to sort the rows. In this example, 3 in the doc1 row and 4 in the doc2 row are used to sort the two rows, and the sorting result is doc2 and doc1. 
    FieldSort fieldSort = new FieldSort("field1", SortOrder.DESC);
    fieldSort.setMode(SortMode.MAX);
}
{
    // If you set the mode parameter to SortMode.MIN, the minimum elements of the Array field are used to sort the rows. In this example, 2 in the doc1 row and 1 in the doc2 row are used to sort the two rows, and the sorting result is doc1 and doc2. 
    FieldSort fieldSort = new FieldSort("field1", SortOrder.DESC);
    fieldSort.setMode(SortMode.MIN);
}

// The doc1 and doc2 rows contain the field1 column of the Nested type. 
// The value of the field1 column in the doc1 row is [{"name":"b", "age":1},{"name":"a", "age":7}]. 
// The value of the field1 column in the doc2 row is [{"name":"a", "age":1},{"name":"c", "age":1},{"name":"d", "age":5}].

{
    // You can specify the mode parameter to determine the elements of the Nested field in the two rows that are used to sort the child rows. 
    // If you set the mode parameter to SortMode.MAX, the maximum elements of the Nested field are used to sort the rows. In this example, 7 in the doc1 row and 5 in the doc2 row are used to sort the two rows by the age column, and the sorting result is doc1 and doc2. 
    FieldSort fieldSort = new FieldSort("field1.age", SortOrder.DESC);
    fieldSort.setMode(SortMode.MAX);
    String path = "field1";
    NestedFilter nestedFilter = new NestedFilter(path, QueryBuilders.matchAll().build());
    fieldSort.setNestedFilter(nestedFilter);
}
{
    // You can specify the mode parameter to determine the elements of the Nested field in the two rows that are used to sort the child rows in which the value of the age column is 1. 
    {
        // If you set the mode parameter to SortMode.MAX, the maximum elements of the Nested field are used to sort the rows. In this example, "b" in the doc1 row and "c" in the doc2 row are used to sort the two rows by the name column, and the sorting result is doc2 and doc1.
        FieldSort fieldSort = new FieldSort("field1.name", SortOrder.DESC);
        fieldSort.setMode(SortMode.MAX);
        String path = "field1";
        NestedFilter nestedFilter = new NestedFilter(path, QueryBuilders.term("field1.age",1).build());
        fieldSort.setNestedFilter(nestedFilter);
    }
    {
        // If you set the mode parameter to SortMode.MIN, the minimum elements of the Nested field are used to sort the rows. In this example, "b" in the doc1 row and "a" in the doc2 row are used to sort the two rows by the name column, and the sorting result is doc1 and doc2. 
        FieldSort fieldSort = new FieldSort("field1.name", SortOrder.DESC);
        fieldSort.setMode(SortMode.MIN);
        String path = "field1";
        NestedFilter nestedFilter = new NestedFilter(path, QueryBuilders.term("field1.age",1).build());
        fieldSort.setNestedFilter(nestedFilter);
    }
}

GeoDistanceSort

You can use GeoDistanceSort to sort the query results by geographical location.

SearchQuery searchQuery = new SearchQuery();
// Sort the results based on the distance from the value in the geo column of the Geopoint type to the coordinate pair (0, 0). 
Sort.Sorter sorter = new GeoDistanceSort("geo", Arrays.asList("0, 0"));
searchQuery.setSort(new Sort(Arrays.asList(sorter)));

Specify a paging method

You can configure the limit and offset parameters or use tokens to page the rows in the response.

Configure the limit and offset parameters

If you do not specify values for the limit and offset parameters, the default values are used. The default value of the limit parameter is 10. The default value of the offset parameter is 0.

SearchQuery searchQuery = new SearchQuery();
searchQuery.setQuery(new MatchAllQuery());
searchQuery.setLimit(100);
searchQuery.setOffset(100);

Use a token

We recommend that you use a token for deep paging because this method has no limits on the paging depth.

If Tablestore cannot read all data that meets the query conditions, Tablestore returns nextToken. You can use nextToken to continue to read the subsequent data.

By default, you can only page backward when you use a token. However, you can cache and use the previous token to page forward because a token is valid during the query.

When you use a token, the sorting method is the same as the method that is used in the previous request. Tablestore sorts data based on the IndexSort parameter by default or based on the method that you specified. You cannot specify the sorting method when you use a token. You cannot configure the offset parameter when you use a token. Data is returned page by page in sequence. This results in a slow query.

private static void readMoreRowsWithToken(SyncClient client) {
    SearchQuery searchQuery = new SearchQuery();
    searchQuery.setQuery(new MatchAllQuery());
    searchQuery.setGetTotalCount(true);// Specify that the total number of rows that meet the query conditions is returned. 
    // Specify the name of the data table. Example: sampleTable. Then, specify the name of the search index. Example: sampleSearchIndex. To obtain the name of the search index, you can query the list of search indexes in the Tablestore console or by using Tablestore SDKs. If you query the list of search indexes in the Tablestore console, you can view the list on the Indexes tab of the Manage Table page. 
    SearchRequest searchRequest = new SearchRequest("<TABLE_NAME>", "<SEARCH_INDEX_NAME>", searchQuery);

    SearchResponse resp = client.search(searchRequest);
    if (!resp.isAllSuccess()) {
        throw new RuntimeException("not all success");
    }
    List<Row> rows = resp.getRows();
    while (resp.getNextToken()!=null) { // If the nextToken value is null in the response, all data is read. 
        // Query the nextToken value. 
        byte[] nextToken = resp.getNextToken();

        {
            // If you need to persist nextToken or transfer nextToken to the frontend page, you can use Base64 to encode nextToken into a string. 
            // Tokens are not strings. If you use new String(nextToken) to encode a token into a string, information about the token is lost. 
            String tokenAsString = Base64.toBase64String(nextToken);
            // Decode the string into bytes. 
            byte[] tokenAsByte = Base64.fromBase64String(tokenAsString);
        }

        // Set the token in this request to the nextToken value in the previous response. 
        searchRequest.getSearchQuery().setToken(nextToken);
        resp = client.search(searchRequest);
        if (!resp.isAllSuccess()) {
            throw new RuntimeException("not all success");
        }
        rows.addAll(resp.getRows());
    }
    System.out.println("RowSize: " + rows.size());
    System.out.println("TotalCount: " + resp.getTotalCount());// Specify that the total number of matched rows instead of the number of returned rows is displayed. 
}

FAQ

• What do I do if no data can be found by calling the Search operation?

• How do I increase the value of the limit parameter to 1000 when I call the Search operation of the search index feature to query data?

• Why does a token become invalid when pagination is used in a search index-based query?

References

• When you use a search index to query data, you can use the following query methods: term query, terms query, match all query, match query, match phrase query, prefix query, range query, wildcard query, geo query, KNN vector query, Boolean query, nested query, and exists query. After you create a search index, you can use the query methods provided by the search index to query data from multiple dimensions based on your business requirements.

  You can sort or paginate rows that meet the query conditions by using the sorting and paging features. For more information, see Perform sorting and paging.

  You can use the collapse (distinct) feature to collapse the result set based on a specific column. This way, data of the specified type appears only once in the query results. For more information, see Collapse (distinct).

• If you want to analyze data in a table, you can call the Search operation to use the aggregation feature or use the SQL query feature. For example, you can query the maximum and minimum values, the sum of the values, and the number of rows. For more information, see Aggregation and SQL query.

• If you want to obtain all rows that meet the query conditions without the need to sort the rows, you can call the ParallelScan and ComputeSplits operations to use the parallel scan feature. For more information, see Parallel scan.