You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
request.required.acks/acks: added support for "all" (-1)
Flag config properties now support explicit +addx,-dely and "all"
Added rd_kafka_last_error() alternative to errno for legacy APIs (#571)
Added rd_kafka_get_err_descs() to retrieve full list of error codes.
Added rd_kafka_partitions_pause/_resume()
Consumer: flush local fetchq for partition(s) and stop fetching
Producer: dont send any ProduceRequests to broker for partition(s)
This is also used when a rebalance_cb is registered between the time of
rebalancing and until the application has called assign() to synchronized state.
Prevents app from receiving messages after a rebalance but before assign()
Keep track of app_offset: last message+1 provided to application (issue #106). This is the "next offset" for the application.
Added log.connection.close to turn off logging of broker-triggered disconnects (issue #437)
Added rd_kafka_mem_free()
Formal C and C++ API docs (doxygen)
Added RdKafka::Message::topic_name().
Allows retreiving message topic (name) for auto consumed topics where we dont have a local Topic object
Add C++ Metadata API (@eugpermar and @incessantier)
Changed topic.metadata.refresh.interval.ms to 5m, must be lower than server idle timeout
Alias some new java client properties (bootstrap.servers, enable.auto.commit)
Increased topic.metadata.refresh.interval.ms to the official default 10 minutes (#363)
Added config property 'socket.blocking.max.ms' to control max socket poll time
Added lazy producer message offset reporting
When 'produce.offset.report' is off, produced offsets will still be reported or the last message in each produced batch.
This means an application can still keep track of offsets (though a bit more roughly) without the cost of per-message offset reports.
Added rd_kafka_yield() to break out of callback loops
Propagate UNKNOWN_TOPIC and UNKNOWN_PARTITION to consumers (issue #348)
Handle broker name and nodeid updates (issue #343)
This also migrates bootstrap brokers to proper brokers if they can be exactly matched by name.
Proper generation and installing of pkg-config .pc files for both C and C++ libraries
Report unsupported compression codecs (on consume) as CONSUMER_ERR ops
RdKafka::Conf->set "socket_cb" and "open_cb" checked for wrong Conf type
Deprecate rd_kafka_set_logger() in favour of rd_kafka_conf_set_log_cb()
Dont reset partition count to zero on metadata topic error
A metadata partition count of 0 is returned by the broker with errors such as "No leader broker" for a topic, since these errors are
typically intermittent we hold on to the existing partition count.
Emit ALL_BROKERS_DOWN if none of the initial bootstrap brokers could be added.
Dont loose messages when partition goes away (and there is no UA partition)
Previously any messages in a partition's queue would be silently lost if a partition went away (and there was no UA partition).
These messages are now properly delivery reported with UNKNOWN_PARTITION.