Returns documents that match a provided text, number, date or boolean value. The provided text is analyzed before matching.
The match query is the standard query for performing a full-text search, including options for fuzzy matching.
Match will also work against semantic_text fields. As semantic_text does not support lexical text search, match queries against semantic_text fields will automatically perform the correct semantic search. Because of this, options that specifically target lexical search such as fuzziness or analyzer will be ignored.
GET /_search{ "query": { "match": { "message": { "query": "this is a test" } } } }
<field>
query
<field>.
The match query analyzes any provided text before performing a search. This means the match query can search text fields for analyzed tokens rather than an exact term.
analyzer
query value into tokens. Defaults to the index-time analyzer mapped for the <field>. If no analyzer is mapped, the indexâs default analyzer is used.
auto_generate_synonyms_phrase_query
true, match phrase queries are automatically created for multi-term synonyms. Defaults to true.
See Use synonyms with match query for an example.
boost
1.0.
Boost values are relative to the default value of 1.0. A boost value between 0 and 1.0 decreases the relevance score. A value greater than 1.0 increases the relevance score.
fuzziness
max_expansions
50.
prefix_length
0.
fuzzy_transpositions
true, edits for fuzzy matching include transpositions of two adjacent characters (ab â ba). Defaults to true.
fuzzy_rewrite
rewrite parameter for valid values and more information.
If the fuzziness parameter is not 0, the match query uses a fuzzy_rewrite method of top_terms_blended_freqs_${max_expansions} by default.
lenient
true, format-based errors, such as providing a text query value for a numeric field, are ignored. Defaults to false.
operator
(Optional, string) Boolean logic used to interpret text in the query value. Valid values are:
OR (Default) For example, a query value of capital of Hungary is interpreted as capital OR of OR Hungary.AND For example, a query value of capital of Hungary is interpreted as capital AND of AND Hungary.minimum_should_match
minimum_should_match parameter for valid values and more information.
zero_terms_query
(Optional, string) Indicates whether no documents are returned if the analyzer removes all tokens, such as when using a stop filter. Valid values are:
none (Default) No documents are returned if the analyzer removes all tokens.all Returns all documents, similar to a match_all query.See Zero terms query for an example.
You can simplify the match query syntax by combining the <field> and query parameters. For example:
GET /_search{ "query": { "match": { "message": "this is a test" } } }
The match query is of type boolean. It means that the text provided is analyzed and the analysis process constructs a boolean query from the provided text. The operator parameter can be set to or or and to control the boolean clauses (defaults to or). The minimum number of optional should clauses to match can be set using the minimum_should_match parameter.
Here is an example with the operator parameter:
GET /_search{ "query": { "match": { "message": { "query": "this is a test", "operator": "and" } } } }
The analyzer can be set to control which analyzer will perform the analysis process on the text. It defaults to the field explicit mapping definition, or the default search analyzer.
The lenient parameter can be set to true to ignore exceptions caused by data-type mismatches, such as trying to query a numeric field with a text query string. Defaults to false.
fuzziness allows fuzzy matching based on the type of field being queried. See Fuzziness for allowed settings.
The prefix_length and max_expansions can be set in this case to control the fuzzy process. If the fuzzy option is set the query will use top_terms_blended_freqs_${max_expansions} as its rewrite method the fuzzy_rewrite parameter allows to control how the query will get rewritten.
Fuzzy transpositions (ab â ba) are allowed by default but can be disabled by setting fuzzy_transpositions to false.
Note
Fuzzy matching is not applied to terms with synonyms or in cases where the analysis process produces multiple tokens at the same position. Under the hood these terms are expanded to a special synonym query that blends term frequencies, which does not support fuzzy expansion.
GET /_search{ "query": { "match": { "message": { "query": "this is a testt", "fuzziness": "AUTO" } } } }
If the analyzer used removes all tokens in a query like a stop filter does, the default behavior is to match no documents at all. In order to change that the zero_terms_query option can be used, which accepts none (default) and all which corresponds to a match_all query.
GET /_search{ "query": { "match": { "message": { "query": "to be or not to be", "operator": "and", "zero_terms_query": "all" } } } }
The match query supports multi-terms synonym expansion with the synonym_graph token filter. When this filter is used, the parser creates a phrase query for each multi-terms synonyms. For example, the following synonym: "ny, new york" would produce:
(ny OR ("new york"))
It is also possible to match multi terms synonyms with conjunctions instead:
GET /_search{ "query": { "match" : { "message": { "query" : "ny city", "auto_generate_synonyms_phrase_query" : false } } } }
The example above creates a boolean query:
(ny OR (new AND york)) city
that matches documents with the term ny or the conjunction new AND york. By default the parameter auto_generate_synonyms_phrase_query is set to true.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4