From d76f71b5d1cb0dd96ce899a34c119331cd21125c Mon Sep 17 00:00:00 2001 From: AndyChen Date: Fri, 27 Oct 2023 18:17:41 +0800 Subject: [PATCH] Update docs/src/main/paradox/migration.md Co-authored-by: Renato Cavalcanti --- docs/src/main/paradox/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/paradox/migration.md b/docs/src/main/paradox/migration.md index 94d55e4d..e3b6aaf4 100644 --- a/docs/src/main/paradox/migration.md +++ b/docs/src/main/paradox/migration.md @@ -8,7 +8,7 @@ The previous version was using an auto-increment column as a primary key and for While in `5.4.0`, the primary key and foreign key on the `event_tag` table have been replaced with a primary key from the `event_journal` table. In order to migrate to the new schema, we made a [**migration script**](https://github.com/akka/akka-persistence-jdbc/tree/master/core/src/main/resources/schema) which is capable of creating the new column, migrate the rows and add the new constraints. -By default, the plugin will behave as in previous version. If you want to use the new `event_tag` keys, you need to multiple-phase rollout: +By default, the plugin will behave as in previous version. If you want to use the new `event_tag` keys, you need to run a multiple-phase rollout: 1. apply the first part of the migration script and then redeploy your application on default settings. 2. apply the second part of the migration script that will migrate the rows and adapt the constraints.