This guide explains how to perform a patch level update. The patch level is the version number “after the second dot”. Example: update from 3.15.2 to 3.15.3.

Special Considerations

This section describes noteworthy changes between individual patch levels.

3.15.2 to 3.15.3

Changes in supported Elasticsearch versions

With 3.15.3, Optimize is dropping support for Elasticsearch 8.13, 8.14 and 8.15. Optimize now supports 8.16 and 8.17. If you are on a lower version of Elasticsearch, you will have to update your Elasticsearch instance before executing the Optimize migration.

3.15.3 to 3.15.4

Changes in supported Elasticsearch versions

With 3.15.4, Optimize is dropping support for Elasticsearch 8.16. Optimize now supports 8.17, 8.18 and 8.19. If you are on a lower version of Elasticsearch, you will have to update your Elasticsearch instance before executing the Optimize migration.

3.15.9 to 3.15.10

Changes in supported Opensearch versions

With 3.15.10, Optimize adding support for Amazon OpenSearch 3.x.x, starting from 3.0.0 and up to latest version.

Spring Boot upgrade

Between Optimize 3.15.9 and 3.15.10, Spring Boot was upgraded from version 3 to version 4. This upgrade may introduce breaking changes depending on your environment and customizations.

Please refer to the official Spring Boot migration guide: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.0-Migration-Guide

Additional considerations

• Logback was upgraded as part of the Spring Boot upgrade. Custom Logback configurations may need adjustments due to stricter parsing and updated conditional configuration support.
• Spring Security configuration was updated. If you customized security-related paths, reverse proxy rules, or public endpoints, verify access after upgrading.
• OAuth2 serialization now relies on Spring Security’s standard Jackson modules. If you customized OAuth2 object serialization, verify authentication and session handling.