47 lines
2.3 KiB
Plaintext
47 lines
2.3 KiB
Plaintext
[[breaking_70_indices_changes]]
|
|
=== Indices changes
|
|
|
|
==== `:` is no longer allowed in index name
|
|
|
|
Due to cross-cluster search using `:` to separate a cluster and index name,
|
|
index names may no longer contain `:`.
|
|
|
|
==== `index.unassigned.node_left.delayed_timeout` may no longer be negative
|
|
|
|
Negative values were interpreted as zero in earlier versions but are no
|
|
longer accepted.
|
|
|
|
|
|
==== `_flush` and `_force_merge` will no longer refresh
|
|
|
|
In previous versions issuing a `_flush` or `_force_merge` (with `flush=true`)
|
|
had the undocumented side-effect of refreshing the index which made new documents
|
|
visible to searches and non-realtime GET operations. From now on these operations
|
|
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.
|
|
|
|
|
|
==== 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.
|
|
|
|
|
|
==== Limit to the difference between max_size and min_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.
|
|
|
|
==== Document distribution changes
|
|
|
|
Indices created with version `7.0.0` onwards will have an automatic `index.number_of_routing_shards`
|
|
value set. This might change how documents are distributed across shards depending on how many
|
|
shards the index has. In order to maintain the exact same distribution as a pre `7.0.0` index, the
|
|
`index.number_of_routing_shards` must be set to the `index.number_of_shards` at index creation time.
|
|
Note: if the number of routing shards equals the number of shards `_split` operations are not supported. |