Enno Runne comments

Results 312 comments of


                                            Enno Runne

[Failure] At-Least-Once One To Conditional should support batching of offsets `withOffsetContext`

In the scheduled build https://travis-ci.org/github/akka/alpakka-kafka/jobs/725973526

[Failure] TransactionsSpec: must complete with messages filtered out and transient failure causing an abort with restartable source

https://travis-ci.org/akka/alpakka-kafka/jobs/640635810#L1385 in #1026

[Failure] TransactionsSpec: must complete with messages filtered out and transient failure causing an abort with restartable source

https://travis-ci.org/akka/alpakka-kafka/jobs/648052161#L446 in master

Consumer.atMostOnceSource repeats messages after consumer group rebalance

Thank you for reporting this. We changed the internals of committing quite a bit in 1.1 and 2.0, something might have slipped in there.

Failed: A consume-transform-produce cycle must complete partitioned source with a sub source failure and rebalance of partitions to second instance, timeout

In the scheduled build https://travis-ci.org/github/akka/alpakka-kafka/jobs/725973527#L953

Producer.committableSink doesn't respect commit settings or apply backpressure

Thank you @gabrielreid for pointing this out. Not taking commit callbacks into account for the backpressure is by design and desired behaviour. But I agree, it could be documented. Not...

Producer.committableSink doesn't respect commit settings or apply backpressure

I wonder if we could come up with something that would support your use with the `CommittingProducerSinkStage`. Can you give an indication of what numbers we're talking about? Do you...

Producer.committableSink doesn't respect commit settings or apply backpressure

What was the idea behind `max-batch = 25`? With the new aggregation of commits in the consumer actor, this only leads to more actor messages being sent to the consumer...

Producer.committableSink doesn't respect commit settings or apply backpressure

> Would it work to just increment and decrement a counter of the currently in-flight `commitAsync` calls in `KafkaConsumerActor#commit`, and trigger the `requestDelayedPoll()` based on that counter? That is one...

Consumer Source with relative offset definitions

I believe this would be best implemented as something that retrieves the current offset and creates subscriptions from those offsets. This would benefit from implementing https://github.com/akka/alpakka-kafka/issues/765 first, I guess.