mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-03-03 17:39:15 +00:00
4632661bc7
We want to upgrade to Lucene 7 ahead of time in order to be able to check whether it causes any trouble to Elasticsearch before Lucene 7.0 gets released. From a user perspective, the main benefit of this upgrade is the enhanced support for sparse fields, whose resource consumption is now function of the number of docs that have a value rather than the total number of docs in the index. Some notes about the change: - it includes the deprecation of the `disable_coord` parameter of the `bool` and `common_terms` queries: Lucene has removed support for coord factors - it includes the deprecation of the `index.similarity.base` expert setting, since it was only useful to configure coords and query norms, which have both been removed - two tests have been marked with `@AwaitsFix` because of #23966, which we intend to address after the merge
69 lines
2.5 KiB
Plaintext
69 lines
2.5 KiB
Plaintext
[[breaking_60_settings_changes]]
|
|
=== Settings changes
|
|
|
|
==== Duplicate keys in configuration file
|
|
|
|
In previous versions of Elasticsearch, the configuration file was allowed to
|
|
contain duplicate keys. For example:
|
|
|
|
[source,yaml]
|
|
--------------------------------------------------
|
|
node:
|
|
name: my-node
|
|
|
|
node
|
|
attr:
|
|
rack: my-rack
|
|
--------------------------------------------------
|
|
|
|
In Elasticsearch 6.0.0, this is no longer permitted. Instead, this must be
|
|
specified in a single key as:
|
|
|
|
[source,yaml]
|
|
--------------------------------------------------
|
|
node:
|
|
name: my-node
|
|
attr:
|
|
rack: my-rack
|
|
--------------------------------------------------
|
|
|
|
==== Coercion of boolean settings
|
|
|
|
Previously, Elasticsearch recognized the strings `true`, `false`, `on`, `off`, `yes`, `no`, `0`, `1` as booleans. Elasticsearch 6.0
|
|
recognizes only `true` and `false` as boolean and will throw an error otherwise. For backwards compatibility purposes, during the 6.x series
|
|
index settings on pre-6.0 indices will continue to work. Note that this does not apply to node-level settings that are stored
|
|
in `elasticsearch.yml`.
|
|
|
|
==== Snapshot settings
|
|
|
|
The internal setting `cluster.routing.allocation.snapshot.relocation_enabled` that allowed shards with running snapshots to be reallocated to
|
|
different nodes has been removed. Enabling this setting could cause allocation issues if a shard got allocated off a node and then
|
|
reallocated back to this node while a snapshot was running.
|
|
|
|
==== Store throttling settings
|
|
|
|
Store throttling has been removed. As a consequence, the
|
|
`indices.store.throttle.type` and `indices.store.throttle.max_bytes_per_sec`
|
|
cluster settings and the `index.store.throttle.type` and
|
|
`index.store.throttle.max_bytes_per_sec` index settings are not
|
|
recognized anymore.
|
|
|
|
==== Store settings
|
|
|
|
The `default` `index.store.type` has been removed. If you were using it, we
|
|
advise that you simply remove it from your index settings and Elasticsearch
|
|
will use the best `store` implementation for your operating system.
|
|
|
|
==== Network settings
|
|
|
|
The blocking TCP client, blocking TCP server, and blocking HTTP server have been removed.
|
|
As a consequence, the `network.tcp.blocking_server`, `network.tcp.blocking_client`,
|
|
`network.tcp.blocking`,`transport.tcp.blocking_client`, `transport.tcp.blocking_server`,
|
|
and `http.tcp.blocking_server` settings are not recognized anymore.
|
|
|
|
==== Similarity settings
|
|
|
|
The `base` similarity is now ignored as coords and query normalization have
|
|
been removed. If provided, this setting will be ignored and issue a
|
|
deprecation warning.
|