Google GitGoogle Git
Sign in
apache/pekko-persistence-jdbc/refs/heads/1.4.x
commit
70006c2d607dcfb02f8f7d6ef853e9dc1fd495bd
[log]
author
PJ Fanning <pjfanning@users.noreply.github.com>
Thu Sep 17 21:22:28 2026 +0100
committer
GitHub <noreply@github.com>
Thu Sep 17 21:22:28 2026 +0100
tree
5d98b62285cff484b6078a3bfc45c356237c6a3b
parent
25448623e8a8862c50aa1444f54d2ded79911a6c [diff]
Increase the migrator integration test patience timeout (#628)

The SQL Server migrator integration tests migrate 3000 legacy events with
one insert per event and one per tag, all sequential, and on the GitHub
runners that takes close to the 10 second PatienceConfig timeout. The
"preserving tags" test timed out on
https://github.com/apache/pekko-persistence-jdbc/pull/624 while the same
test on 1.4.x an hour earlier passed at 17.9s total, so this is a flaky
edge rather than a regression. Raise the timeout to 1 minute, matching
the ask timeout.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 file changed
tree: 5d98b62285cff484b6078a3bfc45c356237c6a3b
  1. .github/
  2. core/
  3. doc/
  4. docs/
  5. integration-test/
  6. migrator/
  7. migrator-integration-test/
  8. project/
  9. scripts/
  10. .asf.yaml
  11. .git-blame-ignore-revs
  12. .gitattributes
  13. .gitignore
  14. .sbtopts
  15. .scala-steward.conf
  16. .scalafmt.conf
  17. build.sbt
  18. CHANGELOG.md
  19. CONTRIBUTING.md
  20. LICENSE
  21. NOTICE
  22. README.md
README.md

Apache Pekko Persistence JDBC

Use JDBC-compatible databases with Pekko Persistence

License

pekko-persistence-jdbc writes journal and snapshot entries to a configured JDBC store. It implements the full pekko-persistence-query API and is therefore very useful for implementing DDD-style application models using Pekko for creating reactive applications.

Please note that the H2 database is not recommended to be used as a production database, and support for H2 is primarily for testing purposes.

Documentation

Community

There are several ways to interact with the Pekko community:

  • GitHub discussions: for questions and general discussion.
  • Pekko dev mailing list: for Pekko development discussions.
  • Pekko users mailing list: for Pekko user discussions.
  • GitHub issues: for bug reports and feature requests. Please search the existing issues before creating new ones. If you are unsure whether you have found a bug, consider asking in GitHub discussions or the mailing list first.

Contributing

Contributions are very welcome! The Apache Pekko team appreciates community contributions by both those new to Pekko and those more experienced.

If you find an issue that you'd like to see fixed, the quickest way to make that happen is to implement the fix and submit a pull request.

Refer to the CONTRIBUTING.md file for more details about the workflow, and general hints on how to prepare your pull request.

You can also ask for clarifications or guidance in GitHub issues directly.