honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Note that cutoff_frequency doesn't handle stacked tokens gracefully

This commit is contained in:
Simon Willnauer 2013-10-14 13:45:57 +02:00
parent 7a7370e3c8
commit 25d6f04f13
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/query-dsl/queries/match-query.asciidoc
View File

@ -97,6 +97,13 @@ The `cutoff_frequency` can either be relative to the number of documents
in the index if in the range `[0..1)` or absolute if greater or equal to in the index if in the range `[0..1)` or absolute if greater or equal to
`1.0`. `1.0`.
Note: If the `cutoff_frequency` is used and the operator is `and`
_stacked tokens_ (tokens that are on the same position like `synonym` filter emits)
are not handled gracefully as they are in a pure `and` query. For instance the query
`fast fox` is analyzed into 3 terms `[fast, quick, fox]` where `quick` is a synonym
for `fast` on the same token positions the query might require `fast` and `quick` to
match if the operator is `and`.
Here is an example showing a query composed of stopwords exclusivly: Here is an example showing a query composed of stopwords exclusivly:
[source,js] [source,js]