Release Notes (1.2.x)

1.2.0

Release notes for Apache Pekko Persistence JDBC 1.2.0. See GitHub Milestone for a fuller list of changes.

This release includes some changes from Akka Persistence JDBC 5.2.0, which have recently become available under the Apache License, Version 2.0.

Schema Changes

If you have a pre-existing Pekko Persistence JDBC database and want to upgrade to 1.2.0, it is encouraged for you to update the table definitions. This is not done automatically. We do not expect that there will be issues if you don’t update the table definitions (unless you try to use new features like Durable State support for MySQL and MariaDB).

Please take care when updating the table definitions. We would recommend backing up your database first and ideally, trying the whole process in a test environment before approaching your production database.

For users migrating from older releases, there are some migration scripts that we provide but you need to apply them yourself. They can be found in our git repo or the source release. The migration-1.2.0 directories can be found for some of the database types that we support. MariaDB users should use the mariadb/migration-1.2.0 instead of the mysql one. Please test the scripts using a test database before trying them in your production database.

  • Change Oracle DELETED column type from CHAR to NUMBER (PR323)
  • Add MariaDB schema support. Pre-existing users can stick with using the MySQL dialect that we already supported. The explicit MariaDB support allows use of Durable State persistence that works well in MariaDB but that relies on a feature not availabe in MySQL (PR367)
  • Implement Durable State handling with MySQL. MariaDB users should prefer the specific MariaDB solution in PR367. (PR378)
  • use NVARCHAR instead of VARCHAR for SQL Server (PR382)

Changes

  • Limit events by tag query ordering sizes (PR381)
1.2.0