This is the multi-page printable view of this section. Click here to print.
Version 7.12
- 1: New Features
- 2: Preview Features (experimental)
- 3: Breaking Changes
- 4: Upgrade Notes
- 5: Change Log
1 - New Features
TODO
Complete this section.2 - Preview Features (experimental)
TODO
Complete this section.3 - Breaking Changes
Warning
Please read this section carefully in case any of the changes affect you.Stroom
Breaking changes relating to Stroom.
TODO
Complete this section.Stroom-Proxy
Breaking changes relating to Stroom Proxy.
TODO
Complete this section.Stroom & Stroom-Proxy
Breaking changes that are common to both Stroom and Stroom Proxy.
TODO
Complete this section.4 - Upgrade Notes
Warning
Please read this section carefully in case any of it is relevant to your Stroom/Stroom-Proxy instance.Upgrade Path
You can upgrade to v7.12.x from any v7.x release that is older than the version being upgraded to.
If you want to upgrade to v7.12.x from v5.x or v6.x we recommend you do the following:
- Upgrade v5.x to the latest patch release of v6.0.
- Upgrade v6.x to the latest patch release of v7.0.
- Upgrade v7.x to the latest patch release of v7.12.
Warning
v7.12 cannot migrate content in legacy formats, i.e. content created in v5/v6. You must therefore upgrade to v7.0.x first to migrate this content, before upgrading to v7.12.x.Java Version
Stroom v7.12 requires Java 25.
Warning
This is different to the java version required for Stroom v7.9 (Java 21).Ensure the Stroom and Stroom-Proxy hosts are running the latest patch release of Java v25.
Configuration File Changes
Common Configuration Changes
These changes are common to both Stroom and Stroom Proxy.
TODO
Complete this section.Stroom’s config.yml
TODO
Complete this section.Stroom-Proxy’s config.yml
TODO
Complete this section.Database Migrations
When Stroom boots for the first time with a new version it will run any required database migrations to bring the database schema up to the correct version.
Warning
It is highly recommended to ensure you have a database backup in place before booting stroom with a new version. This is to mitigate against any problems with the migration. It is also recommended to test the migration against a copy of your database to ensure that there are no problems when you do it for real.On boot, Stroom will ensure that the migrations are only run by a single node in the cluster. This will be the node that reaches that point in the boot process first. All other nodes will wait until that is complete before proceeding with the boot process.
It is recommended however to use a single node to execute the migration.
To avoid Stroom starting up and beginning processing you can use the migrage command to just migrate the database and not fully boot Stroom.
See migrage command for more details.