2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-11-24 07:03:19 -05:00
|
|
|
[[breaking_70_analysis_changes]]
|
|
|
|
|
=== Analysis changes
|
|
|
|
|
|
2019-04-08 21:54:29 -04:00
|
|
|
//NOTE: The notable-breaking-changes tagged regions are re-used in the
|
|
|
|
|
//Installation and Upgrade Guide
|
|
|
|
|
|
|
|
|
|
//tag::notable-breaking-changes[]
|
|
|
|
|
|
|
|
|
|
// end::notable-breaking-changes[]
|
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-11-30 11:54:39 -05:00
|
|
|
==== Limiting the number of tokens produced by _analyze
|
|
|
|
|
|
|
|
|
|
To safeguard against out of memory errors, the number of tokens that can be produced
|
|
|
|
|
using the `_analyze` endpoint has been limited to 10000. This default limit can be changed
|
2017-12-21 10:19:58 -05:00
|
|
|
for a particular index with the index setting `index.analyze.max_token_count`.
|
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2017-12-21 10:19:58 -05:00
|
|
|
==== Limiting the length of an analyzed text during highlighting
|
|
|
|
|
|
|
|
|
|
Highlighting a text that was indexed without offsets or term vectors,
|
|
|
|
|
requires analysis of this text in memory real time during the search request.
|
|
|
|
|
For large texts this analysis may take substantial amount of time and memory.
|
|
|
|
|
To protect against this, the maximum number of characters that will be analyzed has been
|
2018-03-02 11:09:05 -05:00
|
|
|
limited to 1000000. This default limit can be changed
|
2018-04-05 12:41:04 -04:00
|
|
|
for a particular index with the index setting `index.highlight.max_analyzed_offset`.
|
|
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-04-05 12:41:04 -04:00
|
|
|
==== `delimited_payload_filter` renaming
|
|
|
|
|
|
|
|
|
|
The `delimited_payload_filter` was deprecated and renamed to `delimited_payload` in 6.2.
|
|
|
|
|
Using it in indices created before 7.0 will issue deprecation warnings. Using the old
|
|
|
|
|
name in new indices created in 7.0 will throw an error. Use the new name `delimited_payload`
|
|
|
|
|
instead.
|
2018-09-06 08:42:06 -04:00
|
|
|
|
2018-09-27 11:41:38 -04:00
|
|
|
[float]
|
2018-09-06 08:42:06 -04:00
|
|
|
==== `standard` filter has been removed
|
|
|
|
|
|
|
|
|
|
The `standard` token filter has been removed because it doesn't change anything in the stream.
|
2019-01-08 22:42:00 -05:00
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
==== Deprecated standard_html_strip analyzer
|
|
|
|
|
|
|
|
|
|
The `standard_html_strip` analyzer has been deprecated, and should be replaced
|
|
|
|
|
with a combination of the `standard` tokenizer and `html_strip` char_filter.
|
|
|
|
|
Indexes created using this analyzer will still be readable in elasticsearch 7.0,
|
2019-02-21 10:47:02 -05:00
|
|
|
but it will not be possible to create new indexes using it.
|
|
|
|
|
|
|
|
|
|
[float]
|
|
|
|
|
==== The deprecated `nGram` and `edgeNGram` token filter cannot be used on new indices
|
|
|
|
|
|
|
|
|
|
The `nGram` and `edgeNGram` token filter names have been deprecated in an earlier 6.x version.
|
|
|
|
|
Indexes created using these token filters will still be readable in elasticsearch 7.0 but indexing
|
|
|
|
|
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
|
2019-04-04 11:30:37 -04:00
|
|
|
or analyzing documents. Both names should be replaced by `ngram` or `edge_ngram` respectively.
|
