Small fixes to breaking changes docs.
* Move ngram and shingle changes to the analysis section. * Add missing heading for field caps change.
This commit is contained in:
parent
78b955eb86
commit
2ca5f98e05
|
@ -59,3 +59,21 @@ Indexes created using these token filters will still be readable in elasticsearc
|
|||
documents using those filter names will issue a deprecation warning. Using the deprecated names on
|
||||
new indices starting with version 7.0.0 will be prohibited and throw an error when indexing
|
||||
or analyzing documents. Both names should be replaced by `ngram` or `edge_ngram` respectively.
|
||||
|
||||
[discrete]
|
||||
==== Limit to the difference between max_size and min_size in NGramTokenFilter and NGramTokenizer
|
||||
|
||||
To safeguard against creating too many index terms, the difference between `max_ngram` and
|
||||
`min_ngram` in `NGramTokenFilter` and `NGramTokenizer` has been limited to 1. This default
|
||||
limit can be changed with the index setting `index.max_ngram_diff`. Note that if the limit is
|
||||
exceeded a error is thrown only for new indices. For existing pre-7.0 indices, a deprecation
|
||||
warning is logged.
|
||||
|
||||
[discrete]
|
||||
==== Limit to the difference between max_shingle_size and min_shingle_size in ShingleTokenFilter
|
||||
|
||||
To safeguard against creating too many tokens, the difference between `max_shingle_size` and
|
||||
`min_shingle_size` in `ShingleTokenFilter` has been limited to 3. This default
|
||||
limit can be changed with the index setting `index.max_shingle_diff`. Note that if the limit is
|
||||
exceeded a error is thrown only for new indices. For existing pre-7.0 indices, a deprecation
|
||||
warning is logged.
|
||||
|
|
|
@ -112,7 +112,9 @@ Previously, `suggest` stats were folded into `search` stats. Support for the
|
|||
backwards compatibility. Backwards support for the `suggest` metric was
|
||||
deprecated in 6.3.0 and now removed in 7.0.0.
|
||||
|
||||
[discrete]
|
||||
[[remove-field-caps-body]]
|
||||
==== Field capabilities request format
|
||||
|
||||
In the past, `fields` could be provided either as a parameter, or as part of the request
|
||||
body. Specifying `fields` in the request body as opposed to a parameter was deprecated
|
||||
|
|
|
@ -38,24 +38,6 @@ visible to searches and non-realtime GET operations. From now on these operation
|
|||
don't have this side-effect anymore. To make documents visible an explicit `_refresh`
|
||||
call is needed unless the index is refreshed by the internal scheduler.
|
||||
|
||||
[discrete]
|
||||
==== Limit to the difference between max_size and min_size in NGramTokenFilter and NGramTokenizer
|
||||
|
||||
To safeguard against creating too many index terms, the difference between `max_ngram` and
|
||||
`min_ngram` in `NGramTokenFilter` and `NGramTokenizer` has been limited to 1. This default
|
||||
limit can be changed with the index setting `index.max_ngram_diff`. Note that if the limit is
|
||||
exceeded a error is thrown only for new indices. For existing pre-7.0 indices, a deprecation
|
||||
warning is logged.
|
||||
|
||||
[discrete]
|
||||
==== Limit to the difference between max_shingle_size and min_shingle_size in ShingleTokenFilter
|
||||
|
||||
To safeguard against creating too many tokens, the difference between `max_shingle_size` and
|
||||
`min_shingle_size` in `ShingleTokenFilter` has been limited to 3. This default
|
||||
limit can be changed with the index setting `index.max_shingle_diff`. Note that if the limit is
|
||||
exceeded a error is thrown only for new indices. For existing pre-7.0 indices, a deprecation
|
||||
warning is logged.
|
||||
|
||||
[discrete]
|
||||
==== Document distribution changes
|
||||
|
||||
|
|
Loading…
Reference in New Issue