Docs: typo on "frequent"
I replaced "high frequent terms" with "high frequency terms" and "low frequent terms" with "low frequency terms". Alternatively, we could write, "highly frequent terms" and "minimally frequent terms" (or just "rare terms"). Closes #8962
This commit is contained in:
parent
fcb83055de
commit
ceafde41e9
|
@ -81,15 +81,15 @@ change that the `zero_terms_query` option can be used, which accepts
|
|||
.cutoff_frequency
|
||||
The match query supports a `cutoff_frequency` that allows
|
||||
specifying an absolute or relative document frequency where high
|
||||
frequent terms are moved into an optional subquery and are only scored
|
||||
if one of the low frequent (below the cutoff) terms in the case of an
|
||||
`or` operator or all of the low frequent terms in the case of an `and`
|
||||
frequency terms are moved into an optional subquery and are only scored
|
||||
if one of the low frequency (below the cutoff) terms in the case of an
|
||||
`or` operator or all of the low frequency terms in the case of an `and`
|
||||
operator match.
|
||||
|
||||
This query allows handling `stopwords` dynamically at runtime, is domain
|
||||
independent and doesn't require on a stopword file. It prevent scoring /
|
||||
iterating high frequent terms and only takes the terms into account if a
|
||||
more significant / lower frequent terms match a document. Yet, if all of
|
||||
iterating high frequency terms and only takes the terms into account if a
|
||||
more significant / lower frequency terms match a document. Yet, if all of
|
||||
the query terms are above the given `cutoff_frequency` the query is
|
||||
automatically transformed into a pure conjunction (`and`) query to
|
||||
ensure fast execution.
|
||||
|
|
Loading…
Reference in New Issue