|
@@ -17,12 +17,15 @@ contribute to the score.
|
|
|
in <<query-filter-context,filter context>>, meaning that scoring is ignored
|
|
|
and clauses are considered for caching.
|
|
|
|
|
|
-|`should` |The clause (query) should appear in the matching document. In
|
|
|
-a boolean query with no `must` or `filter` clauses, one or more `should` clauses
|
|
|
-must match a document. The minimum number of should clauses to match can
|
|
|
-be set using the
|
|
|
-<<query-dsl-minimum-should-match,`minimum_should_match`>>
|
|
|
-parameter.
|
|
|
+|`should` |The clause (query) should appear in the matching document. If the
|
|
|
+`bool` query is in a <<query-filter-context,query context>> and has a `must` or
|
|
|
+`filter` clause then a document will match the `bool` query even if none of the
|
|
|
+`should` queries match. In this case these clauses are only used to influence
|
|
|
+the score. If the `bool` query is a <<query-filter-context,filter context>>
|
|
|
+or has neither `must` or `filter` then at least one of the `should` queries
|
|
|
+must match a document for it to match the `bool` query. This behavior may be
|
|
|
+explicitly controlled by settings the
|
|
|
+<<query-dsl-minimum-should-match,`minimum_should_match`>> parameter.
|
|
|
|
|
|
|`must_not` |The clause (query) must not appear in the matching
|
|
|
documents. Clauses are executed in <<query-filter-context,filter context>> meaning
|