sergehuber opened a new pull request, #810: URL: https://github.com/apache/unomi/pull/810
## Plain-language summary Operators who upgrade from Unomi 3.0 to 3.1 run Groovy migration scripts while the server is stopped. If a migration run fails partway through and is resumed, rollover index aliases for events and sessions could stay misconfigured. That breaks new writes after restart. This change fixes that resume bug and adds a short manual for contributors so future migration scripts avoid the same mistake. ## What changed * Hoist `3.1.0-configure-rollover-aliases` to a top-level migration step in `migrate-3.1.0-01-tenantDocumentIds.groovy` so resume after failure still configures event/session write aliases (UNOMI-943). * Fail fast in `MigrationUtils.getFileWithoutComments` when a bundled Painless/JSON resource is missing, with the same message as `resourceAsString`. * Add unit test for the missing-resource case. * Add manual section **Writing migration scripts** (`writing-migration-scripts.adoc`): step tracking, nested-step pitfall, idempotent transforms, testing, and a pre-merge checklist. Link from migrations hub, `unomi:migrate` help, and 3.0→3.1 guide. ## Test plan - [x] `mvn -pl tools/shell-commands -am test -Dtest=MigrationUtilsTest` - [ ] CI: unit tests + ES/OS integration matrix (includes `Migrate16xToCurrentVersionIT` migration chain on ES) ## References UNOMI-943 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
