You can use match query (MatchQuery) to query data in a table based on approximate matches. Tablestore tokenizes the values in TEXT columns and the keywords you use to perform match queries based on the analyzer that you specify. Therefore, Tablestore can perform match queries based on the tokens. We recommend that you use match phase query (MatchPhraseQuery) for columns for which fuzzy tokenization is used to ensure high performance in fuzzy queries.
- An OTSClient instance is initialized. For more information, see Initialization.
- A data table is created. Data is written to the table.
- A search index is created for the data table. For more information, see Create search indexes.
|table_name||The name of the data table.|
|index_name||The name of the search index.|
|offset||The position from which the current query starts.|
|limit||The maximum number of rows that you want the current query to return. |
To query only the number of rows that meet the query conditions without returning specific data, you can set limit to 0. This way, Tablestore returns the number of rows that meet the query conditions without specific data from the table.
|get_total_count||Specifies whether to return the total number of rows that meet the query conditions. The default value of this parameter is false, which indicates that the total number of rows that meet the query conditions is not returned. |
If you set this parameter to true, the query performance is compromised.
|query_type||The query type. To use match query, set this parameter to |
|field_name||The name of the column that you want to match. |
You can perform match queries on TEXT columns.
|text||The keyword that is used to match the column values when you perform a match query. |
If the column that you want to match is a TEXT column, the keyword is tokenized into multiple tokens based on the analyzer type that you specify when you create the search index. By default, single-word tokenization is performed if you do not specify the analyzer type when you create the search index.
For example, if the column that you want to match is a TEXT column, you set the analyzer type to single-word tokenization, and you use "this is" as a search keyword, you can obtain query results such as "..., this is tablestore", "is this tablestore", "tablestore is cool", "this", and "is".
|operator||The logical operator. By default, OR is used as the logical operator, which indicates that a row meets the query conditions when the column value contains at least the minimum number of tokens. |
If you set the operator to AND, the row meets the query conditions only when the column value contains all tokens.
|minimum_should_match||The minimum number of matched tokens contained in a column value. |
A row is returned only when the value of the field_name column in the row contains at least the minimum number of matched tokens.
Note minimum_should_match must be used together with the OR logical operator.
|columns_to_get||Specifies whether to return all columns of each row that meets the query conditions. You can configure return_type and return_names for this parameter. |
$request = array( 'table_name' => 'php_sdk_test', 'index_name' => 'php_sdk_test_search_index', 'search_query' => array( 'offset' => 0, 'limit' => 2, 'get_total_count' => true, 'query' => array( 'query_type' => QueryTypeConst::MATCH_QUERY, 'query' => array( 'field_name' => 'text', 'text' => 'ots text php keyword', // 'operator' => QueryOperatorConst::PBAND, 'operator' => QueryOperatorConst::PBOR,// Use minimum_should_match with OR. 'minimum_should_match' => 3 ) ), 'sort' => array( array( 'field_sort' => array( 'field_name' => 'keyword', 'order' => SortOrderConst::SORT_ORDER_ASC ) ), ) ), 'columns_to_get' => array( 'return_type' => ColumnReturnTypeConst::RETURN_SPECIFIED, 'return_names' => array('text') ) ); $response = $otsClient->search($request);