Alpakka 1.0.x

To understand the forces on version numbers, read about Alpakka’s versioning scheme.

1.0.2

Released 2019-05-25

This release fixes a bug in the CSV parser which was introduced in 1.0.1 and makes the CSV parser accept escape characters when there is nothing to escape.

Highlights since 1.0.1

CSV: Fixed bug when last column in last line is empty #1710

See changes per module

Contributors in 1.0.2

Author	Commits	Lines added	Lines removed
2m	16	1079	1047
ennru	9	168	461
sullis	1	1	1
mavericksid	1	1	1

All changes since 1.0.1

closed in 1.0.2

1.0.1

Released 2019-05-16

Highlights since 1.0.0

Akka 2.5.22 #1630 by @sullis
FTP: Support partial file download #1660 by Thomas Gambet, @tgambet
HBase: add source #1648 by takako shimamoto, @shimamoto
AWS SQS: Revise stream element data model #1604 by Michel Davit, @RustedBones api-change
AWS SQS/SNS: Enable Scala 2.13 #1641 dependency-change
AWS S3: Bucket management #1546 and #1608 by Marcin Aman, @MarcinAman
AWS S3: forward proxy support #1639 by Fredrik Wendelboe Løkke, @floekke

See changes per module

Contributors in 1.0.1

Author	Commits	Lines added	Lines removed
ennru	19	968	329
2m	15	1146	277
tgambet	3	848	1435
MarcinAman	2	721	8
raboof	2	28	1
sullis	2	10	9
RustedBones	1	655	384
htmldoug	1	326	106
floekke	1	169	21
mayankbansal93	1	153	0
giena	1	144	11
shimamoto	1	134	6
samidalouche	1	16	1
mayankbansal93	1	13	1
huntc	1	12	11
jcroig	1	8	2
longshorej	1	4	0
matsluni	1	3	2
zingkg	1	2	2
chbatey	1	1	1
shiv4nsh	1	1	0

All changes since 1.0.0

closed in 1.0.1

1.0.0

Released 2019-04-04

With this 1.0.0 release Alpakka is another member of the Akka family promising great Open Source software with the Reactive Manifesto in mind.

By now all modules have been worked with to follow a similar structure so that both the user experience and the contributor experience are transferable across the many modules in Alpakka. The recommended structure for connectors is illustrated by the Reference connector.

Having that said, a few parts make use of the @ApiMayChange annotation to keep the door open for API changes, so that they can evolve more rapidly than other modules within Alpakka.

If you have kept to older versions of Alpakka to avoid multiple upgrades, now is the time to migrate to what it offers with 1.0.

Most artifacts of Alpakka are available for Scala 2.11, 2.12 and 2.13.0-M5.

Alpakka 1.0.0 modules require at least Akka 2.5.21. Some modules built up Akka HTTP 10.1.7.

Compatibility

A major goal before turning to 1.0 was to improve chances all Alpakka modules can evolve without breaking users’ code. There are two sides to that: One is binary-compatibility which effectively means you can replace just the jar with a later version’s jar in your installation and everything will work. This becomes extremely important as soon as you use other libraries that rely on the same jar. They will continue to work without recompilation. The other is source-compatibility which, when upgrading to a later minor version, would not require any code changes. Akka and Alpakka strive for binary-compatibility and source-compatibility, but we do not guarantee source-compatibility.

All modules of Alpakka can be used independently, you may mix Alpakka versions for different libraries. With Akka though, it is important though to be strictly using one version (never blend eg. akka-actor 2.5.21 and akka-stream 2.5.12), and do not use an Akka version lower than the one the Alpakka dependency requires (sometimes Alpakka modules depend on features of the latest Akka release).

Highlights since 1.0-RC1

Official support is now available via Lightbend Platform Subscription for the first modules: Couchbase and CSV (Alpakka Kafka has been supported for a while)
MQTT Streaming has been further stabilized
AWS SQS has been marked “API may change” as there are some improvements coming up (see #1604)