Upgrade notes (2.4 to 2.5)
To upgrade Optimize to version 2.5.0 please perform the following steps first: Migration & Upgrade Instructions.
Here you will find information about:
- known issues,
- changes in the supported environments,
- any unexpected behvavior of Optimize (e.g due to a new feature)
If you intend to make use of the new Multi-Tenancy-Feature you need to perform a full reimport and you also may need to amend your existing reports by selecting the tenant you want the report to be based on
Changes in the plugin system
There are required changes for plugins implementing
If you use such a plugin please perform the following steps:
- in the plugin update the Optimize plugin dependency to version 2.5
- the class
PluginVariableDtonow contains the new field
tenantId. Depending on your plugin implementation it might be necessary to include handling this field to not lose it on import.
- build the new version of the plugin and replace the old jar with the new one
Misinterpreted cron expressions
The configuration of Optimize allows you to define when the history cleanup is triggered. For that, the Cron expression notation is used. However, the values are incorrectly interpreted in Optimize. For example, the
historyCleanup.cronTrigger configuration has the default value
0 1 * * *, which should be 1am every day. Unfortunately, a bug causes this to be interpreted as every hour.
To fix this just use the spring cron expression notation. For instance, the default value for
historyCleanup.cronTrigger would then be
0 0 1 * * *.