v2.5.0
Warning
This version has introduced a regression in which an assert is triggered during PushTelemetry call. This happens when no metric is matched on the client side among those requested by broker subscription.
You won't face any problem if:
- Broker doesn't support KIP-714.
- KIP-714 feature is disabled on the broker side.
- KIP-714 feature is disabled on the client side. This is enabled by default. Set configuration
enable.metrics.push
tofalse
. - If KIP-714 is enabled on the broker side and there is no subscription configured there.
- If KIP-714 is enabled on the broker side with subscriptions that match the KIP-714 metrics defined on the client.
Having said this, we strongly recommend using v2.5.3
and above to not face this regression at all.
confluent-kafka-python v2.5.0
v2.5.0 is a feature release with the following features, fixes and enhancements:
- KIP-107 Added delete_records API. (#1710)
- Added an example to show the usage of the custom logger with
AdminClient
. (#1758) - Improve caching on Schema Registry client. (#1744)
- Removed usage of
strcpy
to enhance security of the client. (#1745) - Removed support for centos6 and centos7. (#1776)
- Fixed invalid write in
OAUTHBEARER/OIDC
extensions copy. (#1745) - Fixed documentation for default value of
operation_timeout
andrequest_timeout
in various Admin apis. (#1710) - Fixed an issue related to import error of
TopicCollection
andTopicPartitionInfo
classes when importing through other module like mypy. (#1764) - Fixed a segfault when
commit
orstore_offsets
consumer method is called incorrectly with errored Message object. (#1754) - Fixed
logger
not working when provided as an argument toAdminClient
instead of a configuration property. (#1758) - Fixed some memory leaks related to
PyDict_SetItem
. (#1710)
confluent-kafka-python is based on librdkafka v2.5.0, see the librdkafka release notes for a complete list of changes, enhancements, fixes and upgrade considerations.