diff --git a/docs/reference/mapping/params.asciidoc b/docs/reference/mapping/params.asciidoc index f4a65aa111df1..79275c40d3f7c 100644 --- a/docs/reference/mapping/params.asciidoc +++ b/docs/reference/mapping/params.asciidoc @@ -8,7 +8,6 @@ parameters that are used by <>: The following mapping parameters are common to some or all field datatypes: * <> -* <> * <> * <> * <> @@ -38,8 +37,6 @@ The following mapping parameters are common to some or all field datatypes: include::params/analyzer.asciidoc[] -include::params/boost.asciidoc[] - include::params/coerce.asciidoc[] include::params/copy-to.asciidoc[] diff --git a/docs/reference/mapping/params/boost.asciidoc b/docs/reference/mapping/params/boost.asciidoc deleted file mode 100644 index 29b56e4692c38..0000000000000 --- a/docs/reference/mapping/params/boost.asciidoc +++ /dev/null @@ -1,81 +0,0 @@ -[[mapping-boost]] -=== `boost` - -Individual fields can be _boosted_ automatically -- count more towards the relevance score --- at query time, with the `boost` parameter as follows: - -[source,console] --------------------------------------------------- -PUT my_index -{ - "mappings": { - "properties": { - "title": { - "type": "text", - "boost": 2 <1> - }, - "content": { - "type": "text" - } - } - } -} --------------------------------------------------- - -<1> Matches on the `title` field will have twice the weight as those on the - `content` field, which has the default `boost` of `1.0`. - -NOTE: The boost is applied only for term queries (prefix, range and fuzzy queries are not _boosted_). - -You can achieve the same effect by using the boost parameter directly in the query, for instance the following query (with field time boost): - -[source,console] --------------------------------------------------- -POST _search -{ - "query": { - "match" : { - "title": { - "query": "quick brown fox" - } - } - } -} --------------------------------------------------- - -is equivalent to: - -[source,console] --------------------------------------------------- -POST _search -{ - "query": { - "match" : { - "title": { - "query": "quick brown fox", - "boost": 2 - } - } - } -} --------------------------------------------------- - - -deprecated[5.0.0, "Index time boost is deprecated. Instead, the field mapping boost is applied at query time. For indices created before 5.0.0, the boost will still be applied at index time."] -[WARNING] -.Why index time boosting is a bad idea -================================================== - -We advise against using index time boosting for the following reasons: - -* You cannot change index-time `boost` values without reindexing all of your - documents. - -* Every query supports query-time boosting which achieves the same effect. The - difference is that you can tweak the `boost` value without having to reindex. - -* Index-time boosts are stored as part of the <>, which is only one - byte. This reduces the resolution of the field length normalization factor - which can lead to lower quality relevance calculations. - -================================================== diff --git a/docs/reference/mapping/types/boolean.asciidoc b/docs/reference/mapping/types/boolean.asciidoc index ab8011a4c56e4..a04405f583b76 100644 --- a/docs/reference/mapping/types/boolean.asciidoc +++ b/docs/reference/mapping/types/boolean.asciidoc @@ -93,11 +93,6 @@ The following parameters are accepted by `boolean` fields: [horizontal] -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be stored on disk in a column-stride fashion, so that it diff --git a/docs/reference/mapping/types/date.asciidoc b/docs/reference/mapping/types/date.asciidoc index 4a9474dcfebf1..12851cc5b35f1 100644 --- a/docs/reference/mapping/types/date.asciidoc +++ b/docs/reference/mapping/types/date.asciidoc @@ -95,11 +95,6 @@ The following parameters are accepted by `date` fields: [horizontal] -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be stored on disk in a column-stride fashion, so that it diff --git a/docs/reference/mapping/types/flattened.asciidoc b/docs/reference/mapping/types/flattened.asciidoc index c50d5fe24513e..d2d9b419dcffc 100644 --- a/docs/reference/mapping/types/flattened.asciidoc +++ b/docs/reference/mapping/types/flattened.asciidoc @@ -131,11 +131,6 @@ The following mapping parameters are accepted: [horizontal] -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, - defaults to `1.0`. - `depth_limit`:: The maximum allowed depth of the flattened object field, in terms of nested diff --git a/docs/reference/mapping/types/ip.asciidoc b/docs/reference/mapping/types/ip.asciidoc index 41a889915fb78..840c15bbbccbb 100644 --- a/docs/reference/mapping/types/ip.asciidoc +++ b/docs/reference/mapping/types/ip.asciidoc @@ -45,11 +45,6 @@ The following parameters are accepted by `ip` fields: [horizontal] -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be stored on disk in a column-stride fashion, so that it diff --git a/docs/reference/mapping/types/keyword.asciidoc b/docs/reference/mapping/types/keyword.asciidoc index e0ee14f99b0d0..62b60f7534965 100644 --- a/docs/reference/mapping/types/keyword.asciidoc +++ b/docs/reference/mapping/types/keyword.asciidoc @@ -43,11 +43,6 @@ The following parameters are accepted by `keyword` fields: [horizontal] -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be stored on disk in a column-stride fashion, so that it diff --git a/docs/reference/mapping/types/numeric.asciidoc b/docs/reference/mapping/types/numeric.asciidoc index e99869c7fe275..dbc1fbbb9858c 100644 --- a/docs/reference/mapping/types/numeric.asciidoc +++ b/docs/reference/mapping/types/numeric.asciidoc @@ -95,7 +95,7 @@ queries. However, they are often retrieved using term-level queries. Consider mapping a numeric identifier as a `keyword` if: -* You don't plan to search for the identifier data using +* You don't plan to search for the identifier data using <> queries. * Fast retrieval is important. `term` query searches on `keyword` fields are often faster than `term` searches on numeric fields. @@ -117,11 +117,6 @@ The following parameters are accepted by numeric types: Try to convert strings to numbers and truncate fractions for integers. Accepts `true` (default) and `false`. -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be stored on disk in a column-stride fashion, so that it diff --git a/docs/reference/mapping/types/range.asciidoc b/docs/reference/mapping/types/range.asciidoc index f0ee2879cfeca..f1fa16beee750 100644 --- a/docs/reference/mapping/types/range.asciidoc +++ b/docs/reference/mapping/types/range.asciidoc @@ -207,11 +207,6 @@ The following parameters are accepted by range types: Try to convert strings to numbers and truncate fractions for integers. Accepts `true` (default) and `false`. -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be searchable? Accepts `true` (default) and `false`. diff --git a/docs/reference/mapping/types/text.asciidoc b/docs/reference/mapping/types/text.asciidoc index f3bbb257fb85a..802511f56f4f1 100644 --- a/docs/reference/mapping/types/text.asciidoc +++ b/docs/reference/mapping/types/text.asciidoc @@ -54,11 +54,6 @@ The following parameters are accepted by `text` fields: Defaults to the default index analyzer, or the <>. -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should global ordinals be loaded eagerly on refresh? Accepts `true` or `false` diff --git a/docs/reference/mapping/types/token-count.asciidoc b/docs/reference/mapping/types/token-count.asciidoc index 69dfdbb31cd5f..8c01f9da40efb 100644 --- a/docs/reference/mapping/types/token-count.asciidoc +++ b/docs/reference/mapping/types/token-count.asciidoc @@ -69,11 +69,6 @@ Indicates if position increments should be counted. Set to `false` if you don't want to count tokens removed by analyzer filters (like <>). Defaults to `true`. -<>:: - - Mapping field-level query time boosting. Accepts a floating point number, defaults - to `1.0`. - <>:: Should the field be stored on disk in a column-stride fashion, so that it diff --git a/docs/reference/query-dsl/dis-max-query.asciidoc b/docs/reference/query-dsl/dis-max-query.asciidoc index ff6590eb66373..186425abd2297 100644 --- a/docs/reference/query-dsl/dis-max-query.asciidoc +++ b/docs/reference/query-dsl/dis-max-query.asciidoc @@ -11,9 +11,6 @@ If a returned document matches multiple query clauses, the `dis_max` query assigns the document the highest relevance score from any matching clause, plus a tie breaking increment for any additional matching subqueries. -You can use the `dis_max` to search for a term in fields mapped with different -<> factors. - [[query-dsl-dis-max-query-ex-request]] ==== Example request @@ -63,4 +60,4 @@ relevance score for the document as follows: If the `tie_breaker` value is greater than `0.0`, all matching clauses count, but the clause with the highest score counts most. --- \ No newline at end of file +-- diff --git a/docs/reference/query-dsl/multi-match-query.asciidoc b/docs/reference/query-dsl/multi-match-query.asciidoc index 650f81d67a5cf..0faa61111e6eb 100644 --- a/docs/reference/query-dsl/multi-match-query.asciidoc +++ b/docs/reference/query-dsl/multi-match-query.asciidoc @@ -286,7 +286,7 @@ GET /_search } -------------------------------------------------- -Also, accepts `analyzer`, <>, `lenient` and `zero_terms_query` as explained +Also, accepts `analyzer`, `boost`, `lenient` and `zero_terms_query` as explained in <>, as well as `slop` which is explained in <>. Type `phrase_prefix` additionally accepts `max_expansions`.