[DOCS] Clarifies the effect of per-field boosting (#63733) (#63745)

jrodewig · joshdevins · web-flow · commit 967ba89f168f · 2020-10-15T09:47:31.000-04:00
The original description of per-field boosting is incorrect. Boosting a
field does not imply that it is more important relative to other fields.
It simply means that the score is multiplied by the supplied boost
value. Due to the differences in each field's term and document
statistics, it's not possible to imply relative importance of fields
based on the per-field boost value alone.

Co-authored-by: Josh Devins &lt;josh.devins@elastic.co&gt;
diff --git a/docs/reference/query-dsl/multi-match-query.asciidoc b/docs/reference/query-dsl/multi-match-query.asciidoc
@@ -59,7 +59,8 @@ GET /_search
 }
 --------------------------------------------------
 
-<1> The `subject` field is three times as important as the `message` field.
+<1> The query multiplies the `subject` field's score by three but leaves the
+`message` field's score unchanged.
 
 If no `fields` are provided, the `multi_match` query defaults to the `index.query.default_field`
 index settings, which in turn defaults to `*`. `*` extracts all fields in the mapping that

Original file line number	Diff line number	Diff line change
`@@ -59,7 +59,8 @@ GET /_search`
`59`	`59`	`}`
`60`	`60`	`--------------------------------------------------`
`61`	`61`
`62`		-<1> The `subject` field is three times as important as the `message` field.
	`62`	+<1> The query multiplies the `subject` field's score by three but leaves the
	`63`	+`message` field's score unchanged.
`63`	`64`
`64`	`65`	If no `fields` are provided, the `multi_match` query defaults to the `index.query.default_field`
`65`	`66`	index settings, which in turn defaults to ``. `` extracts all fields in the mapping that