Use Tablestore SDK for Python to build patterns with * and ? and match data in Keyword or Text fields.
Prerequisites
Install the Tablestore SDK for Python and initialize a client.
Description
A wildcard query uses a pattern that contains wildcard characters to match an indexed field. The matching behavior is similar to SQL LIKE. The * character matches zero or more characters, and the ? character matches any single character. For a Keyword field, the pattern is matched against the complete field value. For a Text field, the pattern is matched against individual tokens, and the pattern is not tokenized. A pattern can contain up to 32 characters and can start with a wildcard. Matching is case-sensitive. To implement behavior similar to SQL NOT LIKE, add WildcardQuery to BoolQuery.must_not_queries. When you call the search method, set the query type to WildcardQuery. For information about field types, see String types.
WildcardQuery(field_name, value, weight=None)
The following example queries rows in which the category field matches the book-* pattern and returns up to 10 rows and the total number of matching rows.
query = WildcardQuery("category", "book-*")
search_query = SearchQuery(
query,
limit=10,
get_total_count=True,
)
response = client.search(
"example_table",
"example_index",
search_query,
ColumnsToGet(return_type=ColumnReturnType.ALL),
)
print(response.total_count)
for row in response.rows:
print(row)
Parameters
Search request
The search method contains the following parameters.
|
Name |
Type |
Description |
|
table_name (required) |
|
The name of the data table. |
|
index_name (required) |
|
The name of the search index. |
|
search_query (required) |
|
The query condition and common query configurations. |
|
columns_to_get (optional) |
|
The return column configuration. If this parameter is not specified, only primary key columns are returned. |
|
routing_keys (optional) |
|
The list of primary key values for custom routing fields. You do not need to specify this parameter if custom routing is not configured. |
|
timeout_s (optional) |
|
The request timeout in seconds. If this parameter is not specified, the client-level timeout is used. |
Query configuration
search_query is of the SearchQuery type and contains the following parameters.
|
Name |
Type |
Description |
|
query (required) |
|
The query condition. Set this parameter to |
|
sort (optional) |
|
The sort order of query results. For more information, see Sort and paginate results. |
|
get_total_count (optional) |
|
Specifies whether to return the total number of matching rows. Default value: |
|
next_token (optional) |
|
The pagination token. Set this parameter to |
|
offset (optional) |
|
The offset from which the current query starts. Use this parameter for shallow pagination. |
|
limit (optional) |
|
The maximum number of rows to return. If this parameter is set to |
|
aggs (optional) |
|
The aggregation configurations. For more information, see Aggregation. |
|
group_bys (optional) |
|
The grouping configurations. For more information, see Aggregation. |
|
collapse_field (optional) |
|
The result collapsing configuration, which removes duplicate results based on a specified field. For more information, see Collapse query results. |
|
highlight (optional) |
|
The summary and highlighting configuration for |
Query condition
search_query.query is of the WildcardQuery type and contains the following parameters.
|
Name |
Type |
Description |
|
field_name (required) |
|
The name of the |
|
value (required) |
|
The query pattern, which can contain up to 32 characters. The |
|
weight (optional) |
|
The relevance weight of the query condition. The value must be a positive floating-point number. This parameter does not affect matching or the number of returned rows. It affects the order only when results are sorted by relevance score. Default value: |
Return columns
columns_to_get is of the ColumnsToGet type and contains the following parameters.
|
Name |
Type |
Description |
|
column_names (optional) |
|
The names of attribute columns to return. Specify this parameter only when |
|
return_type (optional) |
|
The return column mode. |
Response
The search method returns SearchResponse. The following table describes the core fields.
|
Field |
Type |
Description |
|
rows |
|
The rows returned by the current query. The number of rows does not exceed |
|
next_token |
|
The token for the next page. If this field is not empty, pass it to the next request to continue reading. |
|
total_count |
|
The number of matching rows. The value depends on the |
|
is_all_succeed |
|
Indicates whether all index partitions were queried. If the value is |
|
agg_results |
|
The aggregation results. This field is empty if |
|
group_by_results |
|
The grouping results. This field is empty if |
|
search_hits |
|
The search hits, including extended information such as relevance scores, highlights, and matching child rows. |
Tuple-compatible response
Starting from Tablestore SDK for Python 5.2.0, search APIs return response objects instead of tuples. Version 5.1.0 and earlier return tuples directly. In version 5.2.1 and later, you can call SearchResponse.v1_response() to obtain a tuple compatible with earlier versions. For new code, access SearchResponse attributes directly to avoid unpacking errors if response fields are extended.
(
rows,
next_token,
total_count,
is_all_succeed,
agg_results,
group_by_results,
search_hits,
) = response.v1_response()