Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove docs related to index time boosting #51704

Merged
merged 1 commit into from
Jan 31, 2020
Merged

Remove docs related to index time boosting #51704

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions docs/reference/mapping/params.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@ parameters that are used by <<mapping-types,field mappings>>:
The following mapping parameters are common to some or all field datatypes:

* <<analyzer,`analyzer`>>
* <<mapping-boost,`boost`>>
* <<coerce,`coerce`>>
* <<copy-to,`copy_to`>>
* <<doc-values,`doc_values`>>
Expand Down Expand Up @@ -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[]
Expand Down
81 changes: 0 additions & 81 deletions docs/reference/mapping/params/boost.asciidoc
View file
Open in desktop

This file was deleted.

5 changes: 0 additions & 5 deletions docs/reference/mapping/types/boolean.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,11 +93,6 @@ The following parameters are accepted by `boolean` fields:

[horizontal]

<<mapping-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<doc-values,`doc_values`>>::

Should the field be stored on disk in a column-stride fashion, so that it
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/date.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,11 +95,6 @@ The following parameters are accepted by `date` fields:

[horizontal]

<<mapping-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<doc-values,`doc_values`>>::

Should the field be stored on disk in a column-stride fashion, so that it
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/flattened.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,11 +131,6 @@ The following mapping parameters are accepted:

[horizontal]

<<mapping-boost,`boost`>>::

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
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/ip.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,6 @@ The following parameters are accepted by `ip` fields:

[horizontal]

<<mapping-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<doc-values,`doc_values`>>::

Should the field be stored on disk in a column-stride fashion, so that it
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/keyword.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,11 +43,6 @@ The following parameters are accepted by `keyword` fields:

[horizontal]

<<mapping-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<doc-values,`doc_values`>>::

Should the field be stored on disk in a column-stride fashion, so that it
Expand Down
7 changes: 1 addition & 6 deletions docs/reference/mapping/types/numeric.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<<query-dsl-range-query,`range`>> queries.
* Fast retrieval is important. `term` query searches on `keyword` fields are
often faster than `term` searches on numeric fields.
Expand All @@ -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-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<doc-values,`doc_values`>>::

Should the field be stored on disk in a column-stride fashion, so that it
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/range.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<mapping-index,`index`>>::

Should the field be searchable? Accepts `true` (default) and `false`.
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/text.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,11 +54,6 @@ The following parameters are accepted by `text` fields:
Defaults to the default index analyzer, or the
<<analysis-standard-analyzer,`standard` analyzer>>.

<<mapping-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<eager-global-ordinals,`eager_global_ordinals`>>::

Should global ordinals be loaded eagerly on refresh? Accepts `true` or `false`
Expand Down
5 changes: 0 additions & 5 deletions docs/reference/mapping/types/token-count.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <<analysis-stop-tokenfilter,`stop`>>).
Defaults to `true`.

<<mapping-boost,`boost`>>::

Mapping field-level query time boosting. Accepts a floating point number, defaults
to `1.0`.

<<doc-values,`doc_values`>>::

Should the field be stored on disk in a column-stride fashion, so that it
Expand Down
5 changes: 1 addition & 4 deletions docs/reference/query-dsl/dis-max-query.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
<<mapping-boost,boost>> factors.

[[query-dsl-dis-max-query-ex-request]]
==== Example request

Expand Down Expand Up @@ -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.
--
--
2 changes: 1 addition & 1 deletion docs/reference/query-dsl/multi-match-query.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -286,7 +286,7 @@ GET /_search
}
--------------------------------------------------

Also, accepts `analyzer`, <<mapping-boost,`boost`>>, `lenient` and `zero_terms_query` as explained
Also, accepts `analyzer`, `boost`, `lenient` and `zero_terms_query` as explained
in <<query-dsl-match-query>>, as well as `slop` which is explained in <<query-dsl-match-query-phrase>>.
Type `phrase_prefix` additionally accepts `max_expansions`.

Expand Down