Highlights

This release brings a performance improvement to users of PartitionedJournalDao. As explained in the migration guide, a new journal_metadata table is used to store data about each persistence id, to have fast access to it and avoid the usage of the following query:

select max("sequence_number") from "journal" where "persistence_id" = ?.

Please follow the migration guide for examples.

Changes

• Scala 2.13.12
• sbt 1.9.8
• sbt-scalafmt 2.5.2
• sbt-mima-plugin 1.1.3
• postgresql 42.7.1
• scalatest 3.2.17
• logback-classic 1.4.14

Highlights

This release brings major change for journals partitioned by ordering values. (persistence_id, sequence_number) index is now unique and can be (re)built without taking any locks that prevent concurrent inserts, updates, or deletes on the table. In other words migration can be lockless.

See full list of changes: https://github.com/SwissBorg/akka-persistence-postgres/milestone/7?closed=1

Migration from akka-persistence-postgres 0.4.0

New indices need to be created on each partition, to avoid locking production databases for too long, it should be done in 2 steps:

1. manually create indices CONCURRENTLY,
2. deploy new release with migration scripts.

Manually create indices CONCURRENTLY

Execute DDL statements produced by the sample migration script, adapt top level variables to match your journal configuration before executing.

Deploy new release with migration scripts

See sample flyway migration script and adapt top level variables to match your journal configuration.

Changes

• Scala 2.13.11 #342
• sbt 1.9.1 #346
• sbt-scalafmt 2.5.0 #307
• sbt-mima-plugin 1.1.2 #332
• sbt-ci-release 1.5.2 #338
• slick 3.4.1 #299
• slick-pg 0.21.1 #312
• postgresql 42.6.0 #346
• flyway-core 9.20.0 #345
• scalatest 3.2.16 #340
• logback-classic 1.4.8 #344
• scaffeine 5.2.0 #281

Notes

• Updating slick-pg brings a dependency conflict with akka, more precisely between ssl-config-core and akka, since both rely on different versions of scala-parser-combinators. Excludingssl-config-core from akka should be enough to solve any issues. Please refer to here for more information.

Highlights

• Dependencies updates;
• CI builds with Java 17 LTS as well;

Changes

• Scala 2.13.9 #299
• sbt 1.7.2 #299
• scaffeine 5.2.1 #296
• flyway-core 9.4.0 #299
• scalatest 3.2.14 #299
• postgresql 42.5.0 #293
• slick 3.4.1 #299
• slick-pg 0.21.0 #299
• logback-classic 1.4.3 #299
• sbt-mima-plugin 1.1.1 #299

Notes

• Updating slick-pg brings a dependency conflict with akka, more precisely with a ssl-config-core an akka dependency, since both rely on different versions of scala-parser-combinators. Excludingssl-config-core from akka should be enough to solve any issues. Please refer to here for more information.

Highlights

• Dependencies updates;

Changes

• scaffeine 5.2.0 #281
• scalatest 3.2.12 #277
• postgresql 42.3.6 #283
• flyway-core 8.5.11 #280
• slick-pg 0.20.3 #275
• logback-classic 1.2.11 #265
• sbt-mima-plugin 1.1.0 #270

Highlights

• Dependencies updates;

Changes

• Scala 2.13.8 #253
• sbt 1.6.2 #258
• scalatest 3.2.11 #255
• postgresql 42.3.3 #261
• flyway-core 8.5.1 #262

Highlights

• akka-persistence-query is now a Provided dependency and minimum supported version is 2.6.16; #228

Changes

• sbt 1.6.1 #250
• scaffeine 5.1.2 #249
• sbt-scalafmt 2.46 #247
• flyway-core 8.3.0 #246
• logback-classic 1.2.10 #245
• slick-pg, slick-pg_circe-json to 0.20.2 #243

Highlights

• Dependencies updates;
• Drop support for Java 1.8 and Scala 2.12.

This release is focused on updating dependencies.

Highlights

This release brings major change for journals partitioned by ordering values. (persistence_id, sequence_number) index is now unique and can be (re)built without taking any locks that prevent concurrent inserts, updates, or deletes on the table. In other words migration can be lockless.

See full list of changes: https://github.com/SwissBorg/akka-persistence-postgres/milestone/7?closed=1

Migration from akka-persistence-postgres 0.4.0

New indices need to be created on each partition, to avoid locking production databases for too long, it should be done in 2 steps:

1. manually create indices CONCURRENTLY,
2. deploy new release with migration scripts.

Manually create indices CONCURRENTLY

Execute DDL statements produced by the sample migration script, adapt top level variables to match your journal configuration before executing.

Deploy new release with migration scripts

See sample flyway migration script and adapt top level variables to match your journal configuration.

Highlights

This release is focused on updating dependencies and minor bug fixes (#141 ).

See full list of changes: https://github.com/SwissBorg/akka-persistence-postgres/milestone/6?closed=1