Release Notes (1.1.x)

1.1.0-M1

Release notes for Apache Pekko Connectors 1.1.0-M1. See GitHub Milestone for a fuller list of changes. As with all milestone releases, this release is not recommended for production use - it is designed to allow users to try out the changes in a test environment.

Known Issues

Some connectors are not currently tested due to problems with running the tests. Please get in touch if you use these connectors, especially if you have time to help with fixing the issues.

The most notable issues are with:

With OrientDB Connector, it appears that the latest orientdb client only works with OrientDB 3.2 servers. If you use an older version of OrientDB, you may be better off sticking the Pekko Connectors 1.0.x (PR361).

Fixes

  • Close JMS sessions when exceptions happen (PR485).

Additions

  • Scala 3 is now support for the Slick Connector.
  • New connector couchbase3 that uses Couchbase Client v3. The pre-existing couchbase connector still uses the older v2 Client.
  • New connector jakartams which is the Jakarta Messaging equivalent of the JMS connector.
  • aws-spi-pekko-http is now part of Apache Pekko, as opposed to being an externally maintained lib.
  • New pekko-connectors-bom (PR633).

Changes

  • New config for FTP Connector that allows you to choose whether to use the legacy or latest code for FTPS proxies (useUpdatedFtpsClient) (PR171).
  • Kinesis: use stage materializer with IODispatcher instead of injected EC (PR226).
  • Add support for FTPS implicit mode (PR311).
  • Google Common: Use scope config for compute-engine auth (PR313).
  • Google Common: Remove duplicate scopes value in reference.conf (PR314).
  • New config for AMQP Connector that allows you to improve performance by reusing byte arrays (PR592).

Dependency Upgrades

Most dependencies have been upgraded to the latest available version that still supports Java 8 as of release time. Exceptions include:

  • HBase (see Known Issues above)
  • Solr Client was upgraded to v8 (v9 does not support Java 8).
  • Spring - we have pinned our dependency to v5 due to Java 8 support. Similarly, Spring Boot is pinned to v2. We expect that you can use newer versions of Spring if you use newer versions of Java Runtime. If you go this route, please test that it works ok before going to production.
1.1.0-M1+154-6981eaa8*