Release Notes (1.1.x)

Apache Pekko Persistence R2DBC 1.1.x releases support Java 8 and above.

1.1.0

Release notes for Apache Pekko Persistence R2DBC 1.1.0. See GitHub Milestone for 1.1.0-M1 and GitHub Milestone for 1.1.0 for a fuller list of changes.

The dependency on org.postgresql:r2dbc-postgresql is no longer added to our dependency pom.xml
- Users need to add their own explicit dependency if they want to use Postgres (release tested with r2dbc-postgresql 1.0.7.RELEASE)
- We now also support MySQL (see below), so we think it is tidier to make the Postgres and MySQL dependencies optional
change R2dbcExecutor functions that work with getRowsUpdated to return Future[Long] (PR90)
Durable State: support revision in deletes (PR92)
Configuring persistence plugins at runtime (PR194)
- We removed implicit merging of specific plugin configuration (pekko.persistence.r2dbc.journal, pekko.persistence.r2dbc.snapshot, etc.) with shared configuration (pekko.persistence.r2dbc) upon plugin initialization, which means that specific plugin configurations must refer to shared keys explicitly.
- Users with relatively simple configurations for their applications - ones that more or less adhere to reference configuration structure and are merged with reference configuration (by using, for example, ConfigFactory.load) - should be able to migrate without additional changes to configuration.
  - Merging with reference configuration adds explicit shared key references.

We now support Postgres and MySQL in pekko-persistence-r2dbc and pekko-projection-r2dbc
- MySQL users will need to add their own explicit dependency on io.asyncer:r2dbc-mysql (release tested with r2dbc-mysql 1.4.1) (PR175, PR177)
Add ConnectionFactoryOptionsCustomizer (PR171)

1.1.0