Migration guide
editMigration guide
editThis section discusses the changes that you need to be aware of to migrate your application to 8.17.0. For more information about what’s new in this release, see the What’s new in 8.17 and Release notes.
As Elasticsearch introduces new features and improves existing ones, the changes sometimes make older settings, APIs, and parameters obsolete. We typically deprecate obsolete functionality as part of a release. If possible, we support the deprecated functionality for several subsequent releases before removing it. This enables applications to continue working unchanged while you prepare to migrate away from the deprecated functionality.
To get the most out of Elasticsearch and facilitate future upgrades, we strongly encourage migrating away from using deprecated functionality as soon as possible.
To give you insight into what deprecated features you’re using, Elasticsearch:
-
Returns a
Warn
HTTP header whenever you submit a request that uses deprecated functionality. - Logs deprecation warnings when deprecated functionality is used.
- Provides a deprecation info API that scans a cluster’s configuration and mappings for deprecated functionality.
For more information about 8.17, see the What’s new in 8.17 and Release notes. For information about how to upgrade your cluster, see Upgrade Elasticsearch.
- Migrating to 8.18
- Migrating to 8.17
- Migrating to 8.16
- Migrating to 8.15
- Migrating to 8.14
- Migrating to 8.13
- Migrating to 8.12
- Migrating to 8.11
- Migrating to 8.10
- Migrating to 8.9
- Migrating to 8.8
- Migrating to 8.7
- Migrating to 8.6
- Migrating to 8.5
- Migrating to 8.4
- Migrating to 8.3
- Migrating to 8.2
- Migrating to 8.1
- Migrating to 8.0