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

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

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 <josh.devins@elastic.co>
This commit is contained in:
James Rodewig 2020-10-15 09:46:36 -04:00 committed by GitHub
parent 095f979060
commit 41ee8df334
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/reference/query-dsl/multi-match-query.asciidoc
View File

@ -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` 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 index settings, which in turn defaults to `*`. `*` extracts all fields in the mapping that