Releases: akka/akka-persistence-jdbc
Akka Persistence JDBC 3.5.3
Changes
- Include timestamp in PersistentRepr and EventEnvelope #346 by @octonato
- Next artifact detection #341 by @octonato
- Backport #329 - eventsByTag fix #340 by @octonato
- Travis: start DBs via docker-compose instead #256 by @ennru
- Changed deleted field to not null #251 by @feoktant
- events by persistenceid improvements #248 by @WellingR
- Bumps Akka to 2.5.25 (latest) #243 by @ignasi35
- Removed unused test code that relied on deprecated scala xml classes #242 by @WellingR
3.5.2 (2019-06-17)
Changes since v3.5.1
Fixes and improvements
- Support the newly released scala 2.13.0 (#238), thanks to Renato Cavalcanti
3.5.1 (2019-06-03)
Changes since v3.5.0
Fixes and improvements
- Our tests now also run on JDK 11 (#224) thanks to Ruud Welling
- We now also build for scala 2.13.0-RC2 (#230 and #234), thanks to Renato Cavalcanti and Dale Wijnand
Dependency upgrades
- Akka 2.5.20 -> 2.5.23
- Added support for scala 2.13.0-RC2 (we still support 2.11.12 and scala 2.12.8)
- Slick 3.3.0 -> 3.3.1
3.5.0 (2019-02-01)
For use with Akka 2.5.x only, please use the 2.8.0 release for Akka 2.4
Changes since v3.4.0
Fixes and improvements
- We now have support for Microsoft SQL Sever (#200), thanks to Jon Fox
- Improved performance of snapshot retrieval (by not retrieving more than needed) (#218), thanks to Rich Birch
- Improvements have been made for the shutdown of the databases. The changes which have been made are not backwards compatible for users which have implemented their own
SlickDatabaseProvider
. (#193), thanks to Ruud Welling - It is now possible to hide logically deleted events from the queries, this is disabled by default, however the old behaviour is deprecated, as we will no longer support logical deletion in the future. (#191), thanks to Renato Cavalcanti
- Improvements in compatibility with akka-typed. (#204), thanks to Nate Vecchiarelli
- Fixed excessive memory usage when deserializing oracle snapshots, (#216) thanks to Ruud Welling
- Fixes for jndi configuration for shared databases, (#219) thanks to Ruud Welling
The complete list of closed issues can be found on the 3.5.0 milestone on github.
Dependency upgrades
- Akka 2.5.13 -> 2.5.20
- Scala 2.12.5 -> 2.12.8
- Slick 3.2.3 -> 3.3.0
- Our testing dependency for h2 has been downgraded to 1.4.196 because of h2 bugs in 1.4.197. In some cases, you might encounter issues when using akka-peristence-jdbc with h2 1.4.197!
3.4.0 (2018-05-29)
For use with Akka 2.5.x only, please use the 2.8.0 release for Akka 2.4
Changes since v3.3.0
Dependencies upgrades
- Akka 2.5.11 -> 2.5.13
Fixes and improvements
- use snapshot table name in its primary key name (#181), thanks to Daniel Keller,
- Cleaned up test configuration files to make the configuration example more simple (#184)
- Added support for using a shared database (#151)
- In-place updates, needed for data migrations (#183), thanks to Konrad Malawski
- minor improvements on SlickDriver (#187)
- Upgrade to Akka 2.5.13 (#189), thanks to Patrik Nordwall
3.3.0 (2018-03-27)
For use with Akka 2.5.x only, please use the 2.8.0 release for Akka 2.4
Changes since v3.2.0
Dependencies upgrades
- Akka 2.5.9 -> 2.5.11
- Scala 2.12.4 -> 2.12.5
- Slick 3.2.1 -> 3.2.3 (see special note)
- Sbt 0.13.15 to 1.1.1
Slick 3.2.3 special note
Since Slick 3.2.2, the maxConnections
must equal numThreads
. This is to prevent some situations where a deadlock could occur. A warning will be emitted in case maxConnections > numThreads
and a runtime exception will be thrown if maxConnections < numThreads
. Therefore the best possible configuration is maxConnections == numThreads
. See slick/slick#1855 for detailed information.
The reference configuration of this plugin has them set to numThreads = 20
and maxConnections = 20
. You may use other values, but make sure both are equal.
Fixes and improvements
- Ensure that the journal sequence actor name is unique when multiple read journals are used
- Aligned numThreads and maxConnections in the reference config and test configs.
- Merged #165. Scripts enhancements. Thanks to Dmitriy Zakomirnyi.
- Merged #163. Upgrade to sbt-scalariform 1.8.2. Thanks to Sullis
- Merged #174. Make the use of sys.addShutdownHook(db.close()) configurable. Thanks to Daniel Keller
- Merged #167. Upgrade from SBT 0.13.x to SBT 1.1.1 . Thanks to Sullis
3.2.0 (2018-01-22)
For use with Akka 2.5.x only, please use the 2.8.0 release for Akka 2.4
Changes since v3.1.0
- Added possibility for physical deletion of marked journal messages.
To physically delete eventsjdbc-journal.logicalDelete
setting should be set tofalse
. - Akka 2.5.8 -> 2.5.9
- Merged #139. Thanks to Dmitriy Zakomirnyi.
3.1.0 (2017-12-20)
For use with Akka 2.5.x only, please use the 2.8.0 release for Akka 2.4
Changes since v3.0.1
- The internal events by tag implementation could perform poorly in some special cases, this has been resolved. (see #155)
- EventsByTag queries are now executed more efficiently by avoiding re-querying data (see #149)
- The eventsByTag and currentEventsByTag queries are now documented (in scaladoc) to explain the guarantees offered by this plugin (and its caveats).
- Removed dependency on JournalRow in ReadJournalDao.
This is a breaking change for everyone who implements a custom ReadJournalDao. - Updated Scala versions to 2.12.4 / 2.11.12
- Akka 2.5.6 -> 2.5.8
- Merged #139, #140, #141, #143, #145, #146, #148, #14, #152, #153, #154, #157, #158. Thanks to
Renato Cavalcanti, Ruud Welling, Sean Sullivan.
3.0.1 (2017-10-27)
For use with Akka 2.5.x only, please use the 2.8.0 release for Akka 2.4
Changes since v3.0.0
- Align JournalTables with the sql schemas (issue #130)
- Current events by tag fix (issue #124)
- fixes for max ordering jump (issue #126)
- Allow configuration of ask timeout when querying maxOrdering (issue #123)
- Cache dependencies in Travis CI.
- sbt-release 1.0.6
- Akka 2.5.4 -> 2.5.6
- Merged PRs #122, #127, #128, #129, #132, #133, #135. Thanks to Jimin Hsieh,
Renato Cavalcanti, Sean Sullivan,
Ruud Welling, Adam Chaulk.
2.8.0 (2017-10-27)
For use with Akka 2.4.x only, please use release 3.0.1 with Akka 2.5
Changes since v2.7.0
- This is a breaking change! EventsByTag query treats the offset as exclusive instead of inclusive. All users of
the eventsByTag query can now reuse theOffset
from the last receivedEventEnvelope
to resume the query. - Align JournalTables with the sql schemas (issue #130)
- Current events by tag fix (issue #124)
- fixes for max ordering jump (issue #126)
- Allow configuration of ask timeout when querying maxOrdering (issue #123)
- sbt-release 1.0.6
- Merged PRs #122, #127, #128, #129, #132, #133. Thanks to Jimin Hsieh,
Renato Cavalcanti, Sean Sullivan,
Ruud Welling, Adam Chaulk.