swift-kafka-client icon indicating copy to clipboard operation
swift-kafka-client copied to clipboard

Results 36 swift-kafka-client issues
Sort by recently updated
recently updated
newest added

``` $ sw_vers ProductName: macOS ProductVersion: 14.0 BuildVersion: 23A344 $ swift -v Apple Swift version 5.9 (swiftlang-5.9.0.128.108 clang-1500.0.40.1) ``` Checked out `main`: ``` commit 5dbf2fadd2ae30d4a90a1df0b8a02083727ba36a (HEAD -> main, origin/main, origin/HEAD)...

We use kafka headers to store technical information about message. However, it was surprising that there are no headers in KafkaAcknowledgedMessage. Could you advise whether there are plans to add...

good first issue

Currently, even if there are move than 100 events (which is hardcoded), we won't continue polling but call `Task.sleep()` which seems pretty strange. I would like to suggest some adaptive...

area/performance

Currently, messages in `KafkaConsumer` provide messages one by one. That is convenient, however it is not efficient for reading big topics, especially on service recovery. I've made a small experiment...

Sometimes it is nice to know that partition/topic was read to EOF and it is supported by librdkafka. It should be explicitly enabled with property `enable.partition.eof=true` and error is handled,...

Currently, to catch rdkafka specific errors it is required to compare a string, for example: ``` do { try self.kafkaProducer.send(record) return } catch let error as KafkaError where error.description.contains("one possible...

There is an approximate solution for Transactional API for Kafka gsoc. Some ideas that were expressed in https://github.com/swift-server/swift-kafka-gsoc/issues/78#issuecomment-1642042408 There are the following ideas: 1. We might initTransaction and switch state...

It is not something obvious in librdkafka but if we set topic config to default values, config become modified. That may cause unexpected behaviour. For example, I use the following...

Transactional API is required to use Exactly Once Semantics provided by Kafka. One of the ideas how to structure this: - Make new actor `KafkaTransactionalProducer` which supports regular `KafkaProducer` API...

* Currently, we expose more or less all `librdkafka` configurations — do we want to narrow it down to the most basic configurations and expand this on user request /...