A newer version is available. For the latest information, see the current release documentation.
« Transient settings migration guide Migrating to 7.14 »
Elastic Docs ›Elasticsearch Guide [7.17] ›Migration guide

Migrating to 7.15

edit

Migrating to 7.15

edit

This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 7.15.

See also What’s new in 7.17 and Release notes.

Breaking changes

edit

The following changes in Elasticsearch 7.15 might affect your applications and prevent them from operating normally. Before upgrading to 7.15, review these changes and take the described steps to mitigate the impact.

Breaking changes introduced in minor versions are normally limited to security and bug fixes. Significant changes in behavior are deprecated in a minor release and the old behavior is supported until the next major release. To find out if you are using any deprecated functionality, enable deprecation logging.

Deprecations

edit

The following functionality has been deprecated in Elasticsearch 7.15 and will be removed in 8.0. While this won’t have an immediate impact on your applications, we strongly encourage you take the described steps to update your code after upgrading to 7.15.

Significant changes in behavior are deprecated in a minor release and the old behavior is supported until the next major release. To find out if you are using any deprecated functionality, enable deprecation logging.

Indices deprecations

edit
Indices created in Elasticsearch 6.x and earlier versions are deprecated.

Details
In 8.x, Elasticsearch will only read indices created in version 7.0 or above. An 8.x node will not start in the presence of indices created in 6.x or earlier versions of Elasticsearch.

Impact
Before upgrading to an 8.x version, reindex any index created in 6.x or earlier versions with Elasticsearch 7.x. If you no longer need the index, delete it instead. You can use the get index API to check the Elasticsearch version in which an index was created.

GET *,-.*?human=true&filter_path=**.settings.index.version.created_string
The simpleifs index store type is deprecated.

Details
The simplefs value for the index.store.type index setting is now deprecated. Use the niofs value for superior or equivalent performance instead.

Impact
To avoid deprecation warnings, discontinue use of the simpleifs store type in new indices or index templates. Reindex any index using simplefs into one with another store type.

Security deprecations

edit
The accept_default_password setting is deprecated.

Details
In 6.0, we deprecated the accept_default_password cluster setting. We removed support for default passwords in 6.0 but did not remove the setting for backwards compatibility. In 8.0, we will remove the setting.

Impact
To avoid deprecation warnings, discontinue use of the setting.

Native role cache settings are deprecated.

Details
In 5.2, we deprecated the following cluster settings:

  • xpack.security.authz.store.roles.index.cache.max_size
  • xpack.security.authz.store.roles.index.cache.ttl

These native role cache settings have been unused since 5.2, but we did not remove the settings for backwards compatibility. In 8.0, we will remove the settings.

Impact
To avoid deprecation warnings, discontinue use of the settings.

Settings deprecations

edit
Fractional byte size values are deprecated.

Details
In 6.2, we deprecated support for fractional byte size values, such as 23.5pb, in:

  • Cluster settings
  • Index settings
  • Cluster state metadata, such as an ILM policy, that support byte size values

Impact
To avoid deprecation warnings, discontinue use of fractional byte size values in your configurations. Update any existing configurations to use whole values.

« Transient settings migration guide Migrating to 7.14 »