alpakka-kafka
alpakka-kafka copied to clipboard
akka
Alpakka Kafka connector - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka.
Quite a few examples in the docs would be simplified by using the `withContext` variants of consumers and producers. Once the `@ApiMayChange` annotations are removed, these should become the recommended...
There has been a need to query certain Kafka topics with relative offsets, for example last offset, or last offset minus 100, or last offset minus 10 minutes. Currently it...
Versions used : 1.0.3 Akka version: 2.5.19 ``` val control = stream.run() // got the stream from Consumer.committableSource val metrics = control.metrics metrics.foreach(map => logger.debug(s"metrics: ${map.mkString("\n")}")) ``` It throws "java.lang.IllegalStateException:...
# Partitioned source: explore the usefulness of partition assignment handler Alpakka Kafka's partitioned sources are the current tool for use-cases where actions need to be taken per partition when reading...
### Short description Possible performance improvement in producer stage where currently a promise is created for every message send. ### Details Currently the default producer stage [creates a Promise](https://github.com/akka/alpakka-kafka/blob/master/core/src/main/scala/akka/kafka/internal/DefaultProducerStage.scala#L111) for...
### Short description Currently `Transactional.flow` emits elements downstream only after they are acked by a Kafka broker, but not necessarily after they are committed. This is counter intuitive, because it...
### Versions used Akka version: 2.5.20 Alpakka Kafka version: 1.0.1 ### Expected Behavior Using Alpakka Kafka Testkit with defaults should run a simple integration test. ### Actual Behavior Several Akka...
The Alpakka Kafka Testkit has useful administrative functionality, such as creating topics with custom parameters. That is implemented on top of Kafka's AdminClient. This functionality could be refactored to the...
We are experiencing strange consumer behavior causing the consumer to read any message, or no messages anymore. Had to copy-paste parts of the log because of ELK-only output... ``` end...
The hot poll loop which drives the Kafka consumer when there is no demand, but commits to execute might work as good in simpler form. Experiments should show how it...