Struct elasticsearch_dsl::search::queries::full_text::MultiMatchQuery [−][src]
pub struct MultiMatchQuery { /* fields omitted */ }
Expand description
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.
To create a Match query with numeric values:
Query::multi_match(vec!["test"], "search text")
.boost(2)
.name("test");
https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html
Implementations
The way the multi_match query is executed internally depends on the type parameter
Analyzer
used to convert the text in the 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.
pub fn auto_generate_synonyms_phrase_query(
self,
auto_generate_synonyms_phrase_query: bool
) -> Self
pub fn auto_generate_synonyms_phrase_query(
self,
auto_generate_synonyms_phrase_query: bool
) -> Self
If true
,
match phrase
queries are automatically created for multi-term synonyms. Defaults to true
.
See Use synonyms with match query for an example.
Maximum edit distance allowed for matching. See Fuzziness for valid values and more information. See Fuzziness in the match query for an example.
Maximum number of terms to which the query will expand.
Defaults to 50
.
Number of beginning characters left unchanged for fuzzy matching.
Defaults to 0
.
If true
, edits for fuzzy matching include transpositions of two
adjacent characters (ab → ba). Defaults to true
.
Method used to rewrite the query. See the
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.
If true
, format-based errors, such as providing a text query
value for a
numeric
field, are ignored. Defaults to false
.
Boolean logic used to interpret text in the query
value
pub fn minimum_should_match(
self,
minimum_should_match: impl Into<MinimumShouldMatch>
) -> Self
pub fn minimum_should_match(
self,
minimum_should_match: impl Into<MinimumShouldMatch>
) -> Self
Minimum number of clauses that must match for a document to be returned.
See the
minimum_should_match
parameter
for valid values and more information.
Indicates whether no documents are returned if the analyzer
removes
all tokens, such as when using a stop
filter.
Floating point number used to decrease or increase the
relevance scores
of a query. Defaults to 1.0
.
You can use the boost parameter to adjust relevance scores for searches containing two or more queries.
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.
You can use named queries to track which queries matched
returned documents. If named queries are used, the response
includes a matched_queries
property for each hit.
Trait Implementations
Returns the “default value” for a type. Read more
Performs the conversion.
Performs the conversion.
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
Auto Trait Implementations
impl RefUnwindSafe for MultiMatchQuery
impl Send for MultiMatchQuery
impl Sync for MultiMatchQuery
impl Unpin for MultiMatchQuery
impl UnwindSafe for MultiMatchQuery
Blanket Implementations
Mutably borrows from an owned value. Read more