librdkafka
No description set
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / librdkafka
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:libraries:c_c++/librdkafka && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000124 124 Bytes | |
librdkafka.changes | 0000024829 24.2 KB | |
librdkafka.spec | 0000003427 3.35 KB | |
v1.9.2.tar.gz | 0004185493 3.99 MB |
Revision 29 (latest revision is 41)
Marcus Meissner (msmeissn)
accepted
request 1003041
from
Dirk Mueller (dirkmueller)
(revision 29)
- update to 1.9.2: * Added KIP-768 OUATHBEARER OIDC support (by @jliunyu, #3560) * Added KIP-140 Admin API ACL support (by @emasab, #2676) * Consumer: `rd_kafka_offsets_store()` (et.al) will now return an error for any partition that is not currently assigned (through `rd_kafka_*assign()`). This prevents a race condition where an application would store offsets after the assigned partitions had been revoked (which resets the stored offset), that could cause these old stored offsets to be committed later when the same partitions were assigned to this consumer again - effectively overwriting any committed offsets by any consumers that were assigned the same partitions previously. This would typically result in the offsets rewinding and messages to be reprocessed. As an extra effort to avoid this situation the stored offset is now also reset when partitions are assigned (through `rd_kafka_*assign()`). Applications that explicitly call `..offset*_store()` will now need to handle the case where `RD_KAFKA_RESP_ERR__STATE` is returned in the per-partition `.err` field - meaning the partition is no longer assigned to this consumer and the offset could not be stored for commit. * Improved producer queue scheduling. Fixes the performance regression introduced in v1.7.0 for some produce patterns. (#3538, #2912) * Windows: Added native Win32 IO/Queue scheduling. This removes the internal TCP loopback connections that were previously used for timely queue wakeups. * Added `socket.connection.setup.timeout.ms` (default 30s). The maximum time allowed for broker connection setups (TCP connection as well as SSL and SASL handshakes) is now limited to this value. This fixes the issue with stalled broker connections in the case of network or load balancer problems. The Java clients has an exponential backoff to this timeout which is
Comments 0